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

Annotations provide idempotentHint=true and destructiveHint=false, which already signal a safe, repeatable operation. The description adds behavioral context by instructing to include the conversation array for reproduction, which is useful for understanding expected input and purpose. It does not contradict annotations.

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 short sentences, front-loaded with the core purpose and immediately followed by the key usage detail. Every word earns its place; no fluff 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?

The tool is simple with 3 params and no output schema, and annotations cover safety hints. The description gives essential purpose and one important parameter hint, but it could add more context about what happens after reporting (e.g., no response body, or that the message is sent to maintainers). Still, for a bug-report tool, this is passable.

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 mentions the conversation array's role in reproduction but does not explain 'message' or 'context' beyond what the property names imply. The description adds some meaning but not enough to fully offset the lack of schema descriptions.

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 reports a bug, missing feature, or feedback, and mentions including the conversation array for reproduction. This is a specific verb+resource pairing, though it doesn't strongly distinguish from siblings because sibling tools are unrelated (e.g., marketplace, authenticate), so differentiation isn't critical here.

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 when to use the tool (when reporting issues/feedback) and gives a key usage detail (include conversation array). It does not explicitly state when not to use it or mention alternatives, but the context is reasonably clear given the sibling set.

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