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

readOnlyHint=true already establishes the safety profile, so the description's extra value is the response envelope ({ result: [...], _metadata }) and the fact that the pagination token comes from a previous response's _metadata. That is real behavioral context beyond the annotations, though auth/rate-limit behavior and total counts are not mentioned.

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 short sentences plus the endpoint mapping: the resource and returned fields come first, followed by the payload shape. Nothing is padded or redundant.

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 two-optional-parameter read tool with no output schema, the description covers what is returned and how pagination continues. It stops short of describing ordering or whether an empty result is possible, which is a minor gap rather than a blocking one.

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 100%, so page_size and page_token are fully documented in the schema already. The description adds no parameter-level detail beyond implying pagination, which the baseline-3 rule covers.

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 your Marketing Campaigns contact lists') and even names the fields each entry carries (id, name, contact_count). It is trivially distinguishable from siblings like sendgrid_list_templates or sendgrid_list_bounces, which target different resources.

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?

Usage is implied by the verb and resource — an agent can infer this is the tool for enumerating marketing lists — but there is no explicit when-to-use, when-not, or alternative routing. Sibling names make the choice fairly obvious, yet the description itself provides no guidance.

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