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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds value beyond those by naming the four specific actions that will NOT occur (draft creation, email send, sequence enrollment, application creation), giving concreteness to the read-only behavior. No contradiction with annotations.

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?

A single sentence that front-loads the operation ('Preview') followed by the essential safety exclusions. Every word earns its place; there is no redundancy or 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?

For a tool with 8 parameters, 0% schema coverage, and no output schema, the description is too thin. It does not explain what the preview returns, whether output is rendered/personalized copy, how the optional parameters shape the preview, or the role of idempotency_key/request_id. An agent has enough to know it is safe, but not enough to invoke it with confidence.

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% and the description provides no parameter guidance for the 8 inputs. While body/subject/prospect_id are self-explanatory from context, request_id, idempotency_key, outreach_intent_key, personalization_instruction, and job_posting_id remain unexplained; with the schema covering nothing, the description should compensate but does not.

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 states a specific verb and resource ('Preview a one-off prospect outreach draft') and explicitly enumerates what it does NOT do (creating a draft, sending email, enrolling a sequence, creating an application). This clearly distinguishes it from the close sibling yardstick_prospects_outreach_create_draft and other bind/apply tools, so an agent can select it without opening schemas.

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?

The negative side-effect list ('without creating a draft, sending email, enrolling a sequence, or creating an application') gives a strong when-to-use signal: this is the safe, non-committal preview variant. However, it never names the alternative tool (e.g., yardstick_prospects_outreach_create_draft) explicitly or states conditions like 'use this before committing to a draft,' so a small inference gap remains.

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