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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds useful behavioral context: includeLeads controls whether leads are returned, pagination is optional, and a not-found case routes to list_lead_lists. It does not detail response format or pagination mechanics, but the annotation coverage lowers the burden.

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?

Three sentences with no filler. The main purpose is front-loaded, usage guidance follows, and the fallback instruction is clearly separated. Every sentence adds value.

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 relatively simple read tool with annotations covering safety, the description covers the core parameters and error recovery. However, it leaves 'details' vague and does not describe pagination cursor behavior or output shape, and there is no output schema. Still, an agent can likely call the tool correctly with the provided guidance.

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 0%, so the description must compensate. It explicitly explains includeLeads and implies limit/cursor through 'paginated leads,' but it does not clarify cursor semantics, limit bounds/defaults, or the relationship between includeLeads and pagination. The parameter names are self-explanatory, but the description only partially fills the gap left by 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 clearly states the operation: 'Get a lead list by ID with details and optionally paginated leads.' This names the specific resource (lead list), the retrieval action, and the optional data scope, making it easy to distinguish from list/create/update siblings.

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 gives concrete guidance: set includeLeads to true to retrieve leads, and use campaignstack_list_lead_lists if the ID is not found. It does not enumerate all alternative tools or when-not-to-use conditions, but the fallback instruction provides clear routing in the most likely failure case.

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