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

Annotations already indicate readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds context about including the conversation for reproduction, but does not disclose any additional behavioral details (e.g., side effects, internal processes). This is acceptable given annotation coverage.

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, both purposeful. The first states the purpose, the second gives a specific actionable instruction. No filler or redundant information.

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 is simple (3 parameters, no output schema), and the description covers purpose and one parameter. However, missing explanations for 'message' and 'context' leave gaps. It is adequate for a low-complexity tool but not complete.

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, but it only explains the 'conversation' parameter (for reproduction). It does not clarify the meaning of 'message' (the required field) or 'context' (the defaulted string). This is insufficient for an agent to correctly populate all parameters.

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 function: 'Report a bug, missing feature, or send feedback.' This is specific verb+resource, and none of the sibling tools (authenticate, connect, etc.) relate to bug reporting or feedback, so it is well distinguished.

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 provides clear usage context: it is for reporting issues, and it instructs the agent to include the conversation array for reproduction. It does not mention when not to use it, but since there are no alternative tools for this purpose, this is adequate.

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