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

Annotations already declare non-read-only, non-idempotent, non-destructive, open-world behavior, so the bar is lower. The description still adds real value beyond them: it discloses that one feedback record is created for Replo's team and that retries after success produce duplicates (consistent with idempotentHint=false), plus explicit data-exclusion rules (no transcripts, credentials, PII).

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, front-loaded with the purpose and trigger, then parameters, then constraints. Each sentence carries weight, though the content-restriction list is slightly redundant with the schema's own parameter description.

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 usefully states the outcome ('creates one feedback record for Replo's team') and duplicate behavior. Annotations cover the safety profile, and required params are fully documented. Complete enough for an agent to invoke correctly, with only the sibling routing left unaddressed.

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%, so the baseline is 3. The description restates the three parameters (projectId, title, description) and repeats the exclusion guidance already present in the schema's description field, adding little syntactic or format meaning beyond what the schema provides.

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+resource ('Submit a feature request to Replo') and adds the trigger condition (user asks to send feedback about a missing capability). Clear on its own, but it never distinguishes itself from the closely related sibling report_bug, leaving the agent to infer feature-request vs. bug-report routing.

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 a clear when-to-use trigger ('when the user asks to send feedback about a missing capability'), which is more than most definitions offer. However, it names no alternatives or exclusions, so the bug-vs-feature boundary with report_bug is left implicit.

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