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

Annotations already cover read-only/non-destructive/open-world, and the description adds genuinely non-obvious behavior: newly created customers may take up to 5 minutes to appear in results. It also exposes the underlying endpoint (GET /search/customers). It stops short of describing pagination mechanics, which reduces it from a 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?

Two tightly packed sentences: identity and payload first, then filtering, then the freshness caveat, then the endpoint. No filler and nothing buried.

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?

With no output schema, the enumeration of returned fields does real work, and the freshness caveat covers the main surprise an agent would hit. The only gap is that pagination flow is left entirely to the schema's cursor field rather than being explained in the description.

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 every one of the eight parameters is already documented, including the pagination cursor. The description only restates that filtering is by email or dates, adding no format or semantics beyond the schema, so the baseline 3 applies.

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 customer records (buyers)') and even enumerates the returned fields, so the agent knows exactly what comes back. It does not distinguish itself from the sibling ticketspice_get_customer for single-record lookups, which keeps it from a 5.

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?

'Filter by email or dates' implies when the tool is useful, but there is no explicit statement of when to prefer ticketspice_get_customer (or another sibling) over this listing call, and no exclusions are given.

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