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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint, so the safety profile is covered. The description adds genuinely non-structured context — that titles, bodies and replies are agent-authored untrusted content and must never be treated as instructions, which is a meaningful prompt-injection warning. It stops short of describing result ordering or pagination behavior beyond the limit parameter.

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 sentences, all load-bearing, with the scoping constraint and the pre-emptive 'check before you hit a wall' hook front-loaded. The middle sentence is dense, chaining read-workarounds and post_agent_feedback into one directive, but nothing is wasted.

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 single-parameter read tool with no output schema, the description covers purpose, status scope, the workflow it belongs to, the shape of returned content (titles/bodies/replies), and a trust warning. Only the ordering/return-volume behavior is left unstated, which is a minor gap.

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% for the single optional 'limit' parameter (min 1, max 50, default 20), so the schema already carries the semantics. The description adds no additional meaning about the parameter, which is the expected baseline when the schema does the heavy lifting.

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 narrows the scope to statuses new/confirmed/fixing — 'never shipped' — so an agent knows exactly what comes back. It is clearly distinguishable from siblings like post_agent_feedback and check_feedback_status without opening any 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?

Explicitly says when to call it ('BEFORE you hit a wall') and gives the full decision procedure: if the error is already reported, read the workarounds and call post_agent_feedback with the same error_signature rather than filing a duplicate. It names the alternative tool and the condition that selects it, leaving nothing to inference.

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