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

With no annotations provided, the description fully bears the transparency burden. It reveals the tool is free and non-payment-related, but does not disclose whether feedback is anonymous, how it gets processed, whether multiple submissions are allowed, or any rate limits. The lack of behavioral context (e.g., 'This is a one-way communication; no guaranteed response') leaves the agent under-informed.

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 long with no filler. Front-loaded with the key action 'FREE feedback', followed by a concise list of examples. However, the phrase 'No payment' repeats the concept of 'FREE' and could be removed for even tighter structure.

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 low complexity and presence of an output schema (which presumably handles return value documentation), the description covers the basic purpose and some affordances. However, the complete lack of parameter documentation and behavioral transparency makes it merely adequate, not complete.

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%, meaning the description must compensate for all four parameters. It only mentions 'wanted' implicitly via the feedback request and fully ignores 'contact', 'context', and 'category'. The agent has no guidance on format, constraints, or how to fill these fields beyond the schema's basic names.

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: collecting user feedback about missing endpoints, wrong output shapes, price objections, or bugs. The verb 'tell us what you needed but didn't get' is specific, and the examples disambiguate from the 16 sibling tools, none of which suggest feedback collection.

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 explicitly says 'FREE feedback' and 'No payment', which guides usage when to use it (free-form feedback) and hints at when not to (not for paid requests). However, it does not explicitly contrast with siblings or state exclusions like 'do not use for general support questions'.

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