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

Annotations already declare read-only/idempotent safety, and the description adds real behavioral context: newest-page-first ordering, that filtered results are ordered by participant ID, the paging handshake via nextId, and results carrying participant IDs. That is meaningful beyond the safety flags, though it omits rate limits or result-size expectations.

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?

A single dense paragraph with purpose front-loaded and paging guidance immediately after. A couple of clauses (e.g. the campaignId default) restate the schema verbatim, which is mildly redundant but not wasteful.

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 an output schema present, return-shape explanation is unnecessary, and the description still flags that results include participant IDs for the paging loop. Defaults, filtering semantics, ordering, and the pagination contract are all covered for a 4-param nested-object tool.

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 coverage is 75%, so the baseline is 3; the description lifts this by supplying the limit default of 10, which the schema does not state, and by explaining how nextId, metadata filtering, and the campaignId fallback interact. The exact-match/string-comparison nuance for metadata duplicates the schema text rather than extending it.

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 participants in your GrowSurf program') and scopes it with ordering and paging details. It reads distinctly from the singular get_participant sibling by implication, but never names or contrasts any sibling explicitly.

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 concrete usage context: pass the returned nextId to continue paging, and use the metadata filter to look someone up by your own customer ID. It stops short of stating when to prefer this tool over siblings like get_participant or bulk_delete_participants.

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