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

Annotations indicate a non-read-only, idempotent operation. The description adds a security warning about sensitive data ('Do not include agent keys, Bearer tokens...') and notes the feedback is 'authenticated', providing context beyond annotations. No contradiction exists between description and 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?

Three purposeful sentences: function, security warning, fallback. No redundant or filler content; the most important information (what it does) appears first.

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 an output schema present and annotations providing safety profile, the description covers purpose, security constraints, and fallback alternatives. It lacks details on authentication requirements or what 'unavailable' means, but these are minor gaps.

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 only 38% (3 of 8 parameters have descriptions). The description does not clarify parameters like operation, severity, or details; it only warns about content security. This is insufficient to compensate for the low schema coverage.

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 explicitly states 'Submit authenticated MCP, API, payment, or usability feedback to RigorLoop' with a clear verb and resource. This is decisively distinct from sibling tools like create_bounty_draft or get_funding_quote, which focus on bounty/funding workflows.

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?

Provides explicit fallback guidance: 'If this operation is unavailable, use POST /api/v1/agent/feedback or https://rigorloop.com/support.' This tells the agent when to use alternatives. It also enumerates the feedback categories, indicating the intended scope of use.

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