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

Annotations indicate idempotentHint=true, readOnlyHint=false, destructiveHint=false. The description adds that the tool can be used for feedback and missing features, and mentions including conversation for reproduction. It does not contradict annotations, but it doesn't disclose additional behavioral traits like whether it creates a ticket or sends an email, which would be useful. Given annotations cover safety, a 3 is appropriate.

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?

The description is concise, two sentences, and front-loaded with the purpose. It wastes no words, but could be slightly more structured by explicitly listing parameters. Still, it is efficient and clear.

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?

Given the tool has 3 parameters, no output schema, and no schema descriptions, the description is somewhat incomplete. It explains the 'conversation' parameter's purpose but not 'context' or the exact format of 'conversation' (string vs array). The tool is simple, but the description could be more complete for an agent to use 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 description coverage is 0%, so the description must compensate. The description mentions 'conversation array' but the schema has a 'conversation' parameter of type string with default '[]', which is not clearly explained. The 'context' parameter is not mentioned at all. The description adds minimal meaning beyond the schema, leaving the agent uncertain about how to fill 'context' and 'conversation'.

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.' It uses a specific verb ('report') and resource ('bug'), and distinguishes from siblings by covering feedback and missing features, which are not implied by sibling names like 'agger_list_accounts' or 'authenticate'.

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 implies when to use the tool (when reporting bugs, missing features, or feedback) but does not explicitly state when not to use it or mention alternatives. It provides a hint about including the conversation array for reproduction, which is useful but not a full usage guideline.

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