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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is known. The description adds the detail about including conversation for reproduction, which gives context on what the tool expects but does not disclose side effects or response behavior. The description does not contradict annotations, and the additional context is useful but limited.

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 only two sentences long and conveys the purpose, scope, and a key usage hint. Every word earns its place; there is no fluff or repetition.

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's simplicity (3 parameters, no output schema), the description covers the core purpose and one parameter. However, it omits any explanation of the 'message' (the actual report content) and 'context' parameters, which may leave the agent unsure of what to provide. The conversation hint is useful but incomplete for a fully self-sufficient description.

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%, and the description only explicitly explains the 'conversation' parameter ('Include the conversation array with recent messages for reproduction'). The required 'message' parameter and the 'context' parameter are not described, leaving them ambiguous. Since the description fails to compensate for the lack of schema descriptions on two out of three parameters, it adds only partial value.

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.' It names the specific resources (bug, feature, feedback) and distinguishes from sibling tools like authenticate or show_version, which have entirely different purposes.

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 clear context on when to use the tool (for reporting issues or feedback) and provides a usage instruction: 'Include the conversation array with recent messages for reproduction.' It does not explicitly mention alternatives or exclusions, but siblings are unrelated, making the intended usage obvious.

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