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

Annotations only say it is a non-read-only, open-world, non-idempotent write; the description goes far beyond that by disclosing that the text is recorded in Tailwind's analytics and posted to an internal staff channel, that credentials and personal data must never be included, and that the report must be written in English even when conversing in another language. It also sets expectations that nothing is fixed now and no usable result is returned, which prevents the agent from waiting on an outcome.

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?

It is front-loaded correctly — purpose first, then when to use, then safety constraints — and nearly every sentence carries a rule or a disambiguation. It is nonetheless very long for a one-parameter tool, and the Communities/Turbo Groups excursion, while useful, could be tightened without losing its routing value.

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 one-param, open-world write with an output schema present, the description covers everything the agent needs: eligibility, consent flow, content constraints, data-handling rules, language requirement, and the fact that the call produces no actionable return. Nothing essential is missing.

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 coverage is already 100% for the single `description` parameter, but the description still adds real semantic guidance: describe the user's goal and the gap, not a tool name, with a concrete good example ('no way to edit a scheduled Pin's board after creating it') and a bad one ('update_board_v2 missing'). The English-output requirement is an additional constraint the schema does not express.

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 first sentence gives a specific verb and destination: 'Sends a feature request or a missing-capability report to Tailwind's product team.' That is unambiguous about what the tool does. It never distinguishes itself from the close sibling `report_issue`, which an agent could easily confuse with this one, so sibling differentiation is absent.

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?

It states the trigger ('when the user asks to send feedback or a feature request'), the self-initiated path (detect a missing capability, tell the user, offer, send only with consent), and explicit exclusions ('a rejected argument, an expired connection, or an out-of-credits message are not missing capabilities'). It also pre-resolves a specific confusion: Communities/Turbo Groups requests are in scope, while `list_group_boards` for Pinterest group boards is a different feature.

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