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

Annotations indicate idempotentHint=true, readOnlyHint=false, destructiveHint=false. The description does not provide extra behavioral context beyond what annotations state. It mentions to include conversation for reproduction, which is a mild behavioral hint. No contradiction. Given annotations cover basic safety, the description adds acceptable context but does not detail any side effects or auth needs.

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?

Two sentences, front-loaded with the primary purpose, with a quick usage tip. Every word earns its place; no fluff.

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?

The tool has a simple purpose but 3 parameters with no descriptions and no output schema. The description gives some guidance (include conversation) but misses explaining 'context' and 'message' formats. Given low complexity, it's adequate but not excellent.

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 0%, and the description does not explain the 'message' parameter (required) or 'context' and 'conversation' parameters. The description mentions 'Include the conversation array', but does not specify the format or purpose of 'context'. With 0% coverage and significant param explanation missing, the description does not compensate for schema gaps, earning a low score.

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 clearly states the tool's purpose: 'Report a bug, missing feature, or send feedback.' This distinguishes it from sibling tools which focus on create/get/update operations. The main verb 'report' plus the specific resources 'bug, missing feature, feedback' makes the purpose clear.

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?

The description suggests 'Include the conversation array with recent messages for reproduction,' which gives context on how to use the tool effectively. However, it does not explicitly state when to use this vs. alternatives, but that is not critical given the unique purpose of reporting issues. The 'send feedback' part broadens usage beyond just bugs, which add some context.

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