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

Beyond the annotations it discloses the full side-effect chain: details are emailed to the agency team, persisted in a lead database, and answered by a specialist, plus the idempotency warning that every call sends a new request and must not be retried after success. This is exactly the context destructiveHint=true implies but cannot explain; the only gap is that it doesn't say what the tool returns on success or failure.

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?

Seven sentences, all load-bearing: the eligibility gate comes first, then the consent prerequisite, then data handling, then the retry warning, then exclusions. No filler or restatement of the title, and the most important constraint is front-loaded.

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 9-parameter outbound-write tool with annotations and an output schema, the description covers everything an agent needs before calling: who to contact, when it is permitted, what must be shown and confirmed, where the data goes, and that calls are non-idempotent. Return values are covered by the existing output schema.

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 100%, so the schema already defines every field and its constraints. The description still adds meaning by enumerating the exact data set the user must be shown before sending and flagging website and phone as optional, tying the parameters to a consent workflow rather than just a payload.

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 action (requesting a human expert review) and a specific counterparty (212medya, the agency publishing the app), and explicitly narrows it to cases where the user asks to be contacted. It also implicitly separates it from the sibling audit tools by stating it must not be used to save or share audit results.

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 an explicit gate ('only when the user explicitly asks to be contacted'), a required pre-call workflow (show the exact fields, obtain confirmation), and a negative rule (do not use it to save/share audit results, or when the user only wants information). Alternatives — the audit siblings — are effectively pointed at by the exclusion clause.

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