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

Annotations already declare readOnlyHint=false, destructiveHint=false, and non-idempotent behavior, so the safety profile is covered. The description adds that submissions go to a human team (implying asynchronous triage), but says nothing about whether repeated submissions create duplicates, whether contactEmail is required when okToContact is true, or what happens after submission.

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 dense sentences, front-loaded with the action and audience, then immediately the inclusion and exclusion rules. Nothing is redundant and nothing could be cut without losing information.

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 output schema means return values need not be explained, and the annotations cover mutability. However, a six-parameter submission form with zero schema descriptions leaves the agent guessing on optional fields like attemptedAction and the contactEmail/okToContact dependency, which is a real completeness gap.

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% across six parameters, so the description must carry the explanatory load and largely does not. The phrasing "mail formats, workflows, or integrations" loosely gestures at the category enum values (mail_type, improvement, integration), but title, description, okToContact, contactEmail, and attemptedAction get no clarification at all.

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 names a specific verb and resource ("Submit a feature request to the Letter IRL team") and scopes the content to "unsupported capabilities or product improvements." No sibling tool competes for this intent, so the agent can distinguish it without reading further.

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 gives explicit inclusion criteria ("missing mail formats, workflows, or integrations") and explicit exclusions ("not for billing or bug support"), which is genuine when/when-not guidance. It stops short of naming where billing or bug issues should go, so the agent is left to infer the correct alternative route.

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