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

No annotations exist, so the description carries the full burden. It does disclose a real behavioral trait the agent needs for planning — the ~1 Claude call cost — implying a billable, non-executing preview. But it never states the operation is read-only/side-effect-free (i.e., does not send the message), which is the key trait for a preview tool with zero annotation coverage.

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, front-loaded sentences with no padding; the action and the cost caveat both land immediately. Only the misleading 'contact' clause detracts from otherwise tight structure.

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, a preview tool should describe what the rendered example contains and how the search_id relates to the contact. Instead the description leaves the parameter unexplained and the return value undescribed, so an agent cannot confidently invoke it.

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 0% and the sole parameter, 'search_id', is never mentioned by name or explained. Worse, the description frames the target as 'a specific contact', which does not match a search-scoped identifier and may mislead an agent about what the ID refers to.

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?

Specific verb ('Render') plus resource ('example personalized email/LinkedIn message'), and the 'example/Preview' framing separates it from the executing siblings such as sdr_launch_outreach. It does not differentiate from close siblings like sdr_get_outreach_content or preview_agent_email, but the purpose itself is unambiguous.

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?

No when-to-use guidance and no routing to alternatives. With siblings like sdr_get_outreach_content (retrieves stored content), sdr_preview_launch_outreach and sdr_preview_search in the same family, an agent has no stated condition for choosing this one over them.

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