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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description goes further by disclosing the payload's contents (system prompt, history, persona voice, response schema) and the constraint that the cap is enforced downstream in record_message. It doesn't state payload size or token limits, which is the only remaining gap.

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 the core purpose in the first sentence, then layers the working-vs-display distinction and a compact three-step workflow. Every sentence carries actionable information with no 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?

With no output schema, the description compensates by enumerating what the payload contains and tying it to the downstream record_message call. An agent has everything needed to fetch, use, and then persist the drafted message.

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% and the single parameter already documents that prospect_id comes from get_pipeline, so the schema does the work. The description names prospect_id in the workflow but adds no format or syntax beyond what's structured.

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 and resource ('Get the drafting payload for the next outreach message') and immediately distinguishes itself as a working payload rather than a display payload. An agent can separate this from siblings like get_pipeline and record_message without opening either 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 an explicit numbered workflow (call with prospect_id, compose, then call record_message with its signature) and an explicit exclusion ('do NOT dump the prompt or conversation history back to the user'). The daily send cap and where the cap-hit error surfaces are also spelled out.

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