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

No annotations are provided, so the description carries the burden. It discloses a meaningful behavioral trait: the tool costs ~1 Claude call, implying a credit-consuming generation action. However, it doesn't state whether the action persists or sends anything, relying on the word 'preview' to imply non-mutating behavior.

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 short sentences, both adding value: the first states the action and resource, the second the cost. It is concise and front-loaded, though it omits important parameter and usage details that could have been included without much bloat.

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 single-parameter tool with no output schema and no annotations, the description provides the core purpose and cost but misses key context: the meaning of search_id, the shape of the rendered message, and when to prefer this over related preview/content tools. The absence of annotations raises the burden, which the description only partially meets.

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?

The schema has a single search_id parameter with zero description coverage, and the description does not explain what search_id refers to or how it maps to 'a specific contact.' Since the description is the only available source of parameter meaning, this is a clear gap.

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 uses a specific verb ('Render') and resource ('example personalized email/LinkedIn message for a specific contact'), clearly conveying the preview nature. It does not explicitly differentiate from sibling preview tools like preview_linkedin_invite, but the contact-specific and email/LinkedIn scoping gives enough distinction for basic selection.

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?

There is no guidance on when to use this tool versus related siblings such as sdr_get_outreach_content or preview_linkedin_invite. The cost note is a constraint, not a usage criterion, and no exclusions or alternatives are mentioned.

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