Template usage

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

Annotations already establish readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds meaningful behavioral context beyond that: the result is a reference graph rather than analytics, which prevents a common misread of a similarly named tool. It stops short of describing result size, pagination, or ordering, so not a full 5.

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?

Four short labeled blocks that are front-loaded with purpose and each carry distinct information: scope, exclusion, return, and trigger. No redundant restatement of the tool name or annotations.

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?

No output schema exists, and the description compensates by describing the return set ('the campaigns and workflows pointing at this template'). Combined with the safety annotations and the pre-delete/pre-edit use case, an agent has everything needed to select and call this tool correctly.

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 parameter with 100% schema description coverage ('Template UUID'), so the schema already carries the semantics and a baseline of 3 applies. The description's phrase 'this template' confirms but does not extend the schema's meaning.

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?

States a specific verb and resource: 'List the campaigns and workflows that reference a template.' It explicitly distinguishes itself from the closest-sounding sibling by naming plunk_get_campaign_stats and clarifying that this reports references, not delivery metrics.

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?

Gives an explicit 'Use when' trigger (before deleting or editing a template, to see what a change would affect) and an explicit exclusion ('Not for: Delivery numbers'), routing the agent to plunk_get_campaign_stats instead. Both when-to-use and when-not-to-use are covered.

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