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

With annotations only covering the safety profile (readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false), the description carries real weight: it explains the Durable Object desk, fundi reproduction, GitHub filing, issue tracking, history inclusion, and the sign-in requirement. That is rich behavioral context well beyond the 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?

Purpose and behavior are front-loaded and every clause carries information, but the run-on construction and repeated references to fundi make it denser than needed. Still efficient for the amount of workflow it conveys.

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 8 parameters, no required fields, and no output schema, the description does a good job covering the lifecycle, statuses, and auth requirement. It stops short of describing the shape of a listed/filed report, but an agent has enough to invoke it correctly.

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 75%, and the description meaningfully supplements the action enum by describing the outcome of 'get' (filed, picked up, closed) and the failure mode 'retry' addresses. It also reinforces the skill parameter's non-inference rule, though it adds little for kind, severity, or component beyond the schema.

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?

Opens with a specific verb+resource: 'Report a problem with a component or the registry,' and explains the full downstream flow (desk → fundi reproduction → GitHub issue → tracking). It does not, however, differentiate itself from the sibling docs_submit_feedback, which overlaps conceptually given that 'feedback' is a valid kind here.

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 action-level routing: "Use 'list' to see your earlier reports and 'retry' to re-attempt one that drafted but could not be logged," and explains what 'get' returns. The gap is that it never says when to choose this tool over docs_submit_feedback or mzizi_fundi, despite an apparent overlap.

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