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

readOnlyHint=true already establishes this as a safe read, so the description's added value is the endpoint disclosure (GET /api/v1/networkparticipants and its /state and /zipcode variants), which implies the filters map to distinct routes. It does not cover rate limits, response size, or pagination termination behavior.

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 tight sentences with no filler, and the core purpose is front-loaded before the optional filters. The trailing endpoint parenthetical is slightly technical but does earn its place by revealing the separate route variants.

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 zero-required-parameter, read-only list tool with no output schema, the description covers resource identity, filtering, and paging adequately. It stops short of describing what a participant record contains or how paging ends, which keeps it from a 5.

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 all three parameters are already documented, including the 'ignored if state is set' precedence rule. The description only restates 'filter by state or zipcode' and 'page with continuation_token', adding no syntax or format detail beyond 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?

States a specific verb+resource with scope: 'List the health-data network participants (organizations Particle can query)', and the parenthetical clarifies what a participant actually is. This resource is clearly distinct from the patient/data-oriented siblings such as particle_search_patient and particle_get_fhir.

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 explains the optional filters and pagination but never states when this tool should be chosen over alternatives, nor any prerequisites. Usage is implied by the filter semantics rather than explicitly guided, so it lands at the minimum-viable level.

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