Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds real context beyond that: the token changes identity after host confirmation (confirmToken vs manageToken), which is an authorization detail the agent cannot infer. It does not describe the shape of the returned status values, which matters since there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, zero padding: the purpose and the three checked states come first, then the single conditional rule for the token. Nothing is repeated and nothing is buried.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter read tool with full schema coverage and rich annotations, the description covers purpose and the token lifecycle adequately. The main remaining gap is that no output schema exists and the description does not indicate what the status result looks like (booleans, enum states, etc.).

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% and both parameters are documented with a concrete example draftId and a cross-reference to create_draft_meeting's response fields. The description's token sentence largely restates the schema's token description, adding no new syntax or format detail, so the baseline of 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb (본다/check) and resource (draft), and enumerates the three states it inspects: confirmed, paid, voting opened. That is far more precise than a generic 'get status', though it never names a sibling tool or contrasts itself with them (e.g. get_dashboard, create_draft_meeting).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the stated purpose – call it to poll the lifecycle state of a draft. The second sentence gives a conditional rule for which token to supply, which helps correct invocation, but there is no explicit 'when not to use' or pointer to an alternative tool among the many siblings.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.