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

Beyond the annotations (readOnly=false, idempotent=false, openWorld=true), the description discloses the real-world side effect ('Files feedback with Replo's team'), the anti-duplication rule that matters given idempotentHint=false, and a PII guardrail ('Omit credentials and unrelated customer data'). It also constrains fabrication ('never invent evidence, root cause, or severity'), which annotations cannot express.

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 purpose, then constraints, then post-call behavior — a sensible order with no filler sentences. The prose is dense and clause-heavy, cramming evidence standards into long run-ons, but each sentence carries an actionable rule.

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 5-parameter mutation tool with no output schema, it covers purpose, exclusions, evidence standards, privacy, and duplicate avoidance. It omits what the agent gets back (e.g., a report or ticket identifier) and any indication of latency or failure handling if submission fails.

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 80%, and the description adds genuine signal beyond it: errorContext has no schema description but the description tells the agent to put 'observed errors or request IDs' there, and it explains the required evidentiary standard for reproSteps and description. It stops short of format guidance for title or how to mark unknowns syntactically.

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?

The description opens with a specific verb+resource ('Report a credible ... Replo defect') and enumerates the scope (API, MCP, documentation defects). It clearly carves out non-defects ('ordinary bad arguments, missing configuration, and fixable site-code mistakes'), though it never names submit_feature_request, the sibling an agent would most plausibly confuse this with.

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?

It states when to file ('credible user-reported or directly observed'), when not to (bad arguments, missing configuration, site-code mistakes), and post-call behavior ('continue helping with the user's task', 'Do not resubmit the same report after success'). The prerequisite 'Pass projectId from list_projects' is spelled out explicitly.

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