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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered structurally. The description adds real behavioral context beyond that: what 'open' means (never shipped) and that replies contain workarounds worth reading. It does not mention pagination or result ordering, which keeps it short of a 5.

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?

Purpose is front-loaded in the first clause, followed by actionable guidance. Slightly chatty in the closing line ('fastest way to unblock yourself'), but every sentence carries usable content and nothing is redundant.

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 zero-required-parameter, read-only listing tool with annotations covering safety and no output schema, the description supplies what an agent needs: scope, when to call it, and the follow-up action. Missing only return-shape hints (ordering, pagination behavior), which is minor at this complexity.

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 the single 'limit' parameter is fully documented in the schema (including its default of 20 and max of 50). The description adds no syntax or format detail about the parameter, so the baseline 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?

States a specific verb and resource ('List open bug reports in the Agent Workshop') and pins down the exact scope by enumerating the statuses included ('new/confirmed/fixing — never shipped'). An agent can distinguish this from sibling list/search tools without opening the schema.

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?

Gives explicit when-to-use guidance ('Check this BEFORE you hit a wall'), the condition on which to skip it (error already reported → read workarounds), and the recommended alternative action ('post_agent_feedback with the same error_signature ... instead of filing a duplicate'). This is a complete when/when-not/alternative triad.

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