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

Annotations already establish the safe read-only profile, and the description adds genuine context beyond them: spintax is resolved as it will be for that lead, and omitting leadId defaults to the first lead in the campaign. It still does not state that nothing is sent or how the rendering is returned, but it adds meaningful behavioral detail.

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?

Three tight sentences with the core action front-loaded, followed by the rendering behavior and the default. Every sentence adds information and there is no padding.

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 low-complexity, read-only preview with no output schema, the description covers what is rendered, how spintax is handled, and the fallback when leadId is absent. The main gap is not identifying the 'id' parameter's target resource.

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% with two parameters, so the description must carry the load. It usefully explains the leadId default ('first lead in the campaign') but never clarifies what the required 'id' refers to (campaign vs. lead), leaving half the parameters ambiguous.

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 gives a specific verb and resource: 'Render every step and variant for one lead,' which clearly separates it from plain readers like get_campaign or get_campaign_stats. It does not name any sibling tool to route against, so it falls short of the top band's explicit differentiation.

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?

Usage is only implied — an agent can infer this is for previewing how a campaign looks to a specific lead, likely before launch. There is no statement of when to prefer this over get_campaign or set_sequence, and no prerequisites or exclusions are given.

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