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

Annotations already provide context: readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds no behavioral detail beyond instructing to include conversation history, which is more of a usage hint. There is no contract contradiction, but also no significant disclosure about effects or outputs.

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?

Two short sentences, front-loaded with intent and key instruction. No wasted words, structure is practical and highly skimmable.

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 has three parameters, one of which is required, and no output schema. The description explains the overall purpose and one parameter, but fails to explain the meaning or expected content of 'message' and 'context', nor what the agent should expect in return. It's a weak but functional description for a simple reporting tool.

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 solr description coverage is 0%, so the description carries the burden of param explanation. It only clarifies the 'conversation' parameter's role, while the required 'message' parameter and 'context' are left undefined. This is inadequate for relying entirely on the schema.

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 with specific verbs ('report', 'send feedback') and explicitly lists covered targets (bug, missing feature, feedback). It is unambiguously distinct in purpose from siblings like authenticate or show_version.

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 clear when-to-use condition (to report bugs/features/feedback) and practical guidance to include the conversation array for reproduction. It doesn't mention alternatives or exclusions, but the sibling toolset is unrelated, so no exclusions are necessary.

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