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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the description does not need to repeat these. However, the description adds no additional behavioral context (e.g., data being sent to developers, potential latency, or side effects). It only mentions including a conversation array, which is an input hint rather than behavior.

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 a single sentence that front-loads the primary purpose and then provides a specific instruction (include conversation array). There is no redundancy or unnecessary detail.

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?

For a simple reporting tool, the description lacks crucial details: it does not explain the 'context' parameter, does not clarify the format of 'conversation' (string vs array), and does not state what happens after submission (e.g., confirmation, impact). With no output schema, this information is left to the agent's inference, which could lead to misuse.

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 for parameter meaning. It mentions including the conversation array, but the schema defines conversation as a string (likely JSON), not an array, causing potential confusion. The 'message' parameter is self-explanatory, but 'context' is completely unexplained. This is insufficient compensation for full parameter understanding.

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 is a specific verb+resource combination that distinguishes it from sibling tools like authenticate or show_version, which serve completely different functions.

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 usage for reporting bugs/feedback, but it does not provide explicit guidance on when to use this tool over alternatives or when not to use it. Siblings are unrelated, so no conflicts arise, but there is no explicit 'when to use' statement beyond the purpose.

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