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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety and scope are covered. The description adds useful behavioral context by stating that the result includes merge tags and the following step, end, or branch, but it does not mention error behavior for a missing or invalid step.

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?

The definition is a single front-loaded sentence with no redundant wording. Every clause contributes to scope or return-content clarity.

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 one-parameter read tool with no output schema, describing the returned content and branch context is valuable. However, the step_id identifier is unexplained and there is no guidance on when to select this tool over its campaign-level siblings, leaving meaningful gaps.

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?

There is one required parameter, step_id, with zero schema description coverage. The description does not clarify whether this is a campaign-step ID, the relationship to a campaign, or the expected ID format, so it fails to compensate for the missing schema documentation.

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 and resource: read one email of a campaign. It also enumerates what is returned — full content, merge tags, and next-step/branch information — which distinguishes it from get_campaign and get_campaign_draft, though it does not name those siblings explicitly.

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?

It implies usage by saying this reads a single campaign email step rather than the whole campaign, but it gives no explicit when-to-use or when-not-to-use guidance. Alternatives such as get_campaign, get_campaign_draft, or list_campaign_enrollments are not mentioned.

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