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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds the behavioral detail that results include status and step counts, but it doesn't mention pagination or the default limit behavior, especially since the description says 'all' while a limit parameter exists.

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 description is a single concise sentence that is front-loaded with the verb and resource. It contains no filler words and efficiently communicates core purpose.

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 simple list tool with read-only annotations and optional params, the description is mostly complete. It defines the resource and mentions return fields. However, the word 'all' conflicts with the limit parameter's default of 20, which could mislead about pagination. The lack of an output schema is mitigated by mentioning status and step counts.

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 50% (status has a description, limit does not). The description does not explain the limit parameter or provide any additional meaning beyond the schema. It mentions no parameters at all, failing to compensate for the gap.

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 clearly states the tool lists email sequences, clarifying they are multi-step drip campaigns. It also specifies the returned information (status and step counts), distinguishing it from sibling list tools like list_campaigns or list_forms.

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 description implies use for email sequences but does not explicitly contrast with alternatives like list_campaigns or list_segments. It lacks clear when-to-use or when-not-to-use guidance, though the distinct resource name provides some contextual direction.

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