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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is partly covered, but the description adds substantial non-obvious behavior: the compact-summary return shape, that description and source URL are truncated previews with a marker, that reporter contact fields and screenshots are omitted, and a prompt-injection warning about untrusted returned text. That is real context beyond the annotations.

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 sentence one, usage routing follows, then the truncation caveat and the untrusted-data warning. Every sentence carries actionable information with no filler, despite the description being longer than typical.

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 13 parameters, no output schema, and a rich read surface, the description supplies what is missing: return shape, truncation behavior, omitted fields, and a safety warning. An agent has enough to call and interpret the result without guessing.

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 schema already documents every filter, including OR-vs-AND combination semantics and accepted value forms. The description only refers to 'optional filters' generically, adding no syntax or format detail beyond what the schema carries, 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 (List) and resource (feedback/bug reports) scoped to one project, and immediately distinguishes itself from get_feedback by noting it returns many items with pagination and filters. An agent can tell it apart from every sibling without opening a 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 routes to siblings: get_project and list_tags to discover filter values, get_feedback for a single item's full details, list_comments for comment history. It also gives a concrete decision rule ('if a description is marked truncated, call get_feedback before triaging'), which is exactly the kind of when-to-use guidance that prevents wrong tool choice.

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