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

Annotations already declare readOnlyHint=true, so the safe read nature is covered. The description adds the underlying endpoint and its variant paths plus the paging mechanism, which is useful operational context, but it does not say what a response contains or how pagination terminates. Modest added value over the annotation.

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 sentences, front-loaded with the resource and clarified scope, followed by the optional filters and paging. The trailing endpoint note is compact and no sentence is 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 read-only, zero-required-parameter list tool with a fully documented schema and no output schema, the description covers purpose, filters, and pagination adequately. It stops just short of explaining the continuation_token's origin/termination or the response shape.

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 (state, zipcode, continuation_token) are already documented, including the state-over-zipcode precedence. The description restates the same filters and paging without adding format or boundary details, so 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+resource ('List the health-data network participants') and clarifies with a parenthetical what a participant is ('organizations Particle can query'). This is readily distinguishable from the sibling patient/query/document tools, which all operate on clinical data rather than the network directory.

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 implies usage via the optional filters and paging, and the schema notes zipcode is ignored when state is set. However, it never states when an agent should reach for this tool versus siblings like particle_search_patient, nor any prerequisites (e.g., auth scope) — guidance is implied rather than explicit.

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