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

Annotations indicate idempotentHint=true, but the description does not discuss behavior beyond the basic function. It mentions including conversation array for reproduction, which is useful, but does not disclose potential side effects (e.g., sending data externally) or clarify the idempotent nature. Without annotations like readOnlyHint, the description carries burden but only partially addresses it.

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, efficient and front-loaded with the purpose. It earns its place by adding the reproduction hint, but could be slightly more structured without being verbose.

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 there is no output schema and low schema coverage, the description is incomplete. It doesn't explain what response to expect, nor does it fully describe each parameter's purpose. The tool's complexity is low, but for a feedback tool, more context on data usage and expected outcomes would be beneficial.

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 for parameter meaning. It mentions 'conversation array' for reproduction, which clarifies the conversation parameter, but does not explain 'message' or 'context' beyond schema. The description provides minimal additional semantics for the required 'message' parameter.

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 states the tool reports a bug, missing feature, or feedback, which is a clear purpose. It distinguishes from siblings like 'marketplace' or 'authenticate', but could be more specific about the action (e.g., 'creates a report').

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 context on when to use (reporting bugs/feedback) but does not explicitly state when not to use or name alternatives. It implies usage for reporting issues, but lacks explicit guidance on when other tools might be more appropriate.

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