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

Annotations declare idempotentHint=true and readOnlyHint=false, and the description does not contradict these. However, beyond the purpose, the description adds only the note about including the conversation for reproduction, which is more of a usage hint than a behavioral disclosure. It does not mention whether the report is sent, stored, triggers notifications, or requires authentication, leaving the agent without insight into side effects or requirements.

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, consisting of two sentences with no wasted words. It is front-loaded with the primary purpose and quickly provides a usage hint. While it is short, this is not a case of over-condensation; the brevity is appropriate given the tool's simplicity, though it could be more structured with parameter guidance.

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 tool with three parameters and no output schema, the description is insufficient. It does not explain the return format (if any), fully describe parameter usage, or provide clarity on the expected behavior. The presence of basic annotations does not compensate for the lack of details about how the tool interacts with the system. It is a minimally functional description but not complete enough for an agent to confidently use it.

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?

With 0% schema description coverage, the description is responsible for explaining all parameters. It only mentions the conversation parameter ('Include the conversation array with recent messages'), implying it is for reproduction, but does not clarify the required 'message' parameter or the optional 'context' parameter. The meaning of 'message' must be inferred from the tool purpose, and 'context' is left entirely unexplained. This is a significant gap.

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 the listed siblings, none of which relate to reporting issues. The purpose is unambiguous and covers the expected use cases.

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 gives a partial usage guideline by instructing to include the conversation array for reproduction, which indicates when this tool is appropriate (for issues that need reproduction steps). However, it does not explicitly state when to use this tool versus any alternatives, nor does it list any prerequisites or exclusions. It provides context but not a full when-to-use vs. when-not-to-use explanation.

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