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

Annotations already provide safety/intent hints (readOnly=false, destructive=false, idempotent=true). The description adds the meaningful behavioral note about including conversation messages for reproduction, but it does not disclose what happens after reporting (e.g., ticket creation, notifications), and it does not address how the idempotent hint should be interpreted in the context of duplicate reports.

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 two sentences, front-loading the core purpose first, then a single targeted usage instruction. Every word earns its place with no filler or redundancy.

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 3-parameter, no-output tool with annotations, the description gives enough to invoke it: purpose and reproduction guidance. It would be slightly more complete with a note about what the user should expect as a response, but the tool's simplicity and existing annotation coverage keep the gap minimal.

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. It does explain the 'conversation' parameter ('include the conversation array with recent messages for reproduction'), which adds value beyond the raw schema. However, it does not clarify the required 'message' parameter or the optional 'context' parameter, leaving gaps in 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 starts with a specific, action-oriented verb ('Report') and names the full scope: a bug, a missing feature, or feedback. It clearly distinguishes this tool from its unrelated siblings (authenticate, connect, marketplace, etc.) by establishing it as the feedback channel.

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 sentence 'Report a bug, missing feature, or send feedback' provides explicit context for when this tool should be used. It also instructs users to include the conversation array for reproduction, which is practical guidance, though it does not explicitly state when to avoid using the tool or list alternatives.

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