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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds ordering semantics, signature-group deduplication, the fact that `member_id_sample` is truncated at 8 while `instance_count` is the true total, and that `instances_path` holds the remainder. These are non-obvious behavioral traits an agent could not infer from structured fields.

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?

Front-loaded with 'Start here.' and the highest-priority result class before the fallback inbox. Dense with backticked field names in a single paragraph; every clause carries information but the packing slightly hurts scanability.

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?

With no output schema, the description carries the return-shape burden and does so well (row = signature group, `id` is best member, sample vs. full counts). Missing only parameter guidance for `limit`/`projectId`, a minor gap for an otherwise self-contained definition.

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 only 33%: `since` is documented, but `limit` and `projectId` are described nowhere. The description spends its words on return-value semantics rather than parameter meaning, so the coverage gap is not compensated — though both undocumented params are conventional and appear across sibling list tools.

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?

Concrete verb + resource with explicit scope: returns person-sent bugs first, then a deduplicated critical/high (or regression) inbox. It directly names the sibling it replaces ('Use this instead of list_bugs'), so an agent can discriminate it 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?

'Start here' plus 'Use this instead of list_bugs for what to work on' gives an explicit when-to-use and names the alternative. It also states exclusion conditions (diagnostic, silenced, agent-acked rows) so the agent knows what will not appear.

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