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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds genuine behavioral context beyond structured fields: the polling model, the fact that ask_issue_question does not block, and that state='all' includes withdrawn/expired items. It does not describe return fields or pagination behavior, so not a top score.

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?

Three tight sentences, front-loaded with the tool's purpose and modes, then the polling rationale, then defaults. Little redundancy and no filler.

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 read-only list tool with no output schema, the description covers modes, defaults, and filtering behavior adequately. The shape of returned questions (fields, answer-option structure) is only implied, a minor gap given the absent output schema.

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 coverage is 100%, so the baseline is 3. The description nevertheless frames what each role mode means in operational terms (what is waiting on YOU, what YOU asked), and clarifies the conditional defaulting between key and role, adding interpretive value over the raw schema.

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?

States the specific verb (list) and resource (issue questions), and immediately distinguishes the three modes: waiting on you (role='to_me'), you asked (role='asked'), or everything on one issue. It is clearly separable from siblings like ask_issue_question and answer_issue_question.

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?

Explicitly tells the agent when to use this tool — to find out whether a question you asked has been answered — and explains that ask_issue_question does not wait, so polling is required. Defaults (role='to_me' with no key, every question with a key; open-only unless state='all') are stated directly.

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