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

With no annotations, the description carries the burden and does disclose a real output constraint: the result is one presentation slide capped at 6 steps, which materially shapes how an agent should call it. It also states the remediation path for longer processes. It stops short of saying what the call returns (chart ID) or whether the chart lands in a workspace/share page, leaving a modest gap.

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?

Front-loaded with the definition, then the exclusion, then sizing guidance and the follow-up path — a sensible priority order. It is slightly repetitive around step count ("Aim for 4-6 steps", "at most 6", then the edit_chart fallback), which could be tightened into one clause.

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 two-parameter creation tool with no annotations and no output schema, the description covers purpose, the sibling it replaces, sizing expectations, per-step content quality, and the escalation path. An agent has everything needed to call it correctly and to know when to call something else instead.

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 100%, so the schema already documents steps, label, description, icon, key, and id, and the description's "1-2 sentence description per step" largely restates the schema's own description field. It adds a step-count recommendation, but that recommendation ("aim for 4-6 steps") mildly conflicts with the schema's "3-7 is ideal", which could confuse an agent about the intended length.

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?

"Create a sequential/chevron chart: a linear sequence of steps, phases, or stages" names a specific verb and resource and defines the visual shape, with concrete examples (onboarding steps, project phases). It explicitly excludes branching logic and names create_flowchart as the tool for that case, so an agent can separate the two without opening either schema.

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?

The definition gives an explicit negative rule ("NOT for branching logic — use create_flowchart for that") plus a positive usage context (linear sequences, presentation-ready slides). It also prescribes the follow-up path for out-of-scope inputs: use edit_chart set_presentation_steps when the process exceeds one slide.

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