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

Annotations provide readOnlyHint=false and idempotentHint=true, but the description adds little behavioral context beyond the concept of sending/reporting. It does not explain what side effects occur, whether the report is stored, whether confirmation is given, or how retries might behave, despite the idempotentHint being somewhat surprising for a feedback/report tool.

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 with no filler. It front-loads the purpose and then gives the key usage hint, making it easy to scan and act on.

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, no output schema, and zero schema description coverage, the description leaves major gaps: the purpose of message/context, the expected conversation format, and what the caller should expect after the call. The reproduction hint is useful, but not sufficient for confident invocation.

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, but it only explains the conversation parameter's role in reproduction. The required message parameter is not explained, and context is completely undocumented, leaving the agent to infer their meaning from parameter names alone.

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 a clear verb-resource pair: reporting a bug, missing feature, or sending feedback. It is immediately distinguishable from sibling tools such as authenticate, marketplace, and search_tools, which serve unrelated 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 implies when to use it: when the user wants to report a bug, request a feature, or give feedback. It also gives a specific instruction to include recent messages for reproduction, but it does not explicitly discuss when not to use it or mention any alternative tool.

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