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

Annotations only declare the generic write/openWorld/non-idempotent profile; the description adds the consequential behavior an agent actually needs: user consent required before sending, PII/credential prohibitions, that the Modem team replies to the given email, and that the call returns a feedback event id. This goes well beyond the structured hints.

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?

Front-loads purpose, then usage, then parameter-filling instructions, so scanning order matches decision order. It is dense with nested parenthetical conditions, which costs some readability, but for a 9-parameter tool every sentence adds real instruction rather than filler.

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?

Covers the consent workflow, the required-vs-optional field split, nested object contents (tags, context), the enum decision, and the return value despite there being no output schema. Nothing an agent needs to invoke this correctly is absent.

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?

With 0% schema description coverage the description carries the full burden and delivers: content and length guidance for message (4096), when each category enum applies, tool_name/trace_id/context for failures, release, and the reply semantics of name/email. Only url is left unexplained, a minor gap against otherwise rich compensation.

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?

States a specific verb+resource ('Send feedback about Modem to the Modem team') and clearly separates itself from the sibling create_feedback_channel, which manages channels rather than transmitting feedback. An agent can identify the operation without opening the schema.

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?

Gives explicit triggering conditions for each category (tool failure/unclear error → agent_friction; user frustration/missing capability → user_feedback) and a hard when-not rule: 'Call it only when the user asks to or agrees, never on your own.' The consent protocol (tell them what you will send, and when it is sent) closes the loop.

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