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

Annotations already declare this is a safe read (readOnlyHint=true, openWorldHint=false), so the bar is lower, and the description still adds value by disclosing the response shape and its deterministic ordering rule for branches (true path before false). It does not mention behavior for an unknown campaign_id or whether the payload is paginated/truncated for large campaigns.

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 tight sentences with no filler: the return shape and ordering rule come first, followed by the actionable id-reuse warning. The parenthetical about branch ordering earns its space because it defines an otherwise unpredictable result order.

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, the description does the work of sketching return contents (steps, ids, traversal order), which is the most important thing for a reader to know before calling. It stops short of indicating which campaign-level fields come back (name, status, audience) or error behavior, leaving a modest gap for a read tool whose safety profile is already covered by annotations.

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 a single required parameter, campaign_id, with 0% schema description coverage, so the description is the only place semantics could be added — yet it never mentions the parameter. The phrase "Read a campaign" makes the identifier's meaning obvious enough that no real ambiguity results, but nothing is added beyond the schema.

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 ("Read a campaign") and adds scope detail: it returns every step in walk order, which implicitly separates it from get_campaign_step (single step) and get_campaign_draft. It does not explicitly name those siblings, so an agent must infer the boundary rather than being told.

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 a real usage rule — take step ids from this response and use them to edit, never re-create a step — which is actionable workflow guidance. However, there is no statement of when to prefer this over list_campaigns, get_campaign_step, or get_campaign_draft, so alternative selection is left to inference.

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