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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real behavioral detail beyond that: filters are conjoined (not OR-ed), results are paged and the next_page token is fed back into the page parameter, and the underlying endpoint is disclosed. Missing are auth requirements and default ordering.

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?

Four short sentences, front-loaded with the resource coverage and followed by filter and paging rules; every sentence carries information. The trailing 'GET /main/Organization' is near-redundant with the schema and could be dropped without loss.

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 description could say more about what an organization record contains or the default result ordering. Still, for a read-only, all-optional-parameter list tool it covers coverage, filtering semantics, id format, and pagination well enough to call correctly.

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 the baseline is 3. The description earns a bump by mapping the profile enum values to plain-language categories (practice group, clinic, funder, external practice) and by explaining how next_page relates to the page parameter, adding meaning beyond the raw schema strings.

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?

The description uses a specific verb ('List or search') and enumerates the exact resource kinds covered (practice group, clinic locations, funders, external practices), plus the id shape PG-12345. It does not explicitly contrast itself with halaxy_get_organization or other list siblings, but the list/search framing is unambiguous.

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?

'Filters combine with AND' and the paging instruction give useful operational context, but there is no explicit when-to-use guidance: nothing says when to prefer halaxy_get_organization for a known id, or what happens when zero filters are supplied (full listing vs. error). Usage is implied rather than stated.

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