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

With no annotations, the description carries the full burden and does unusually well: it discloses the ordering rule and explicitly denies payment influence ('ordered by how much information an organization provides, never by payment'), explains the meaning of `verified.status` unclaimed (not reviewed by USAnaru™), and scopes results to organization-level public facts with no contact people. It omits result-set size, pagination, and any access/permission notes, which keeps it below 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 dense sentences with no filler; the resource definition and its sub-categories lead, followed by filters and output semantics. The second sentence is long and packs several distinct facts (verified flag, programs, city/state, website, URL, ordering) into one clause chain, which costs a little readability but no sentences are wasted.

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 compensates by naming the returned fields (`verified.status`, programs, office city/state, website, page URL) and the ordering criterion, which is exactly what an agent needs to interpret results. The remaining gap is operational: nothing is said about result limits, pagination, or behavior when an enum combo yields no matches across a 6-parameter filter surface.

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 83%, so the baseline is 3, but the description adds real value by disambiguating two easily confused parameters: `lang` (language of returned page URLs/facet names) versus `language` (language the organization works in), and by clarifying that `country` is where the family lives rather than where the organization operates. It restates the enum values for visa (f1, j1) and kind rather than exceeding the schema there.

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 precisely names the resource — organizations serving international families with U.S. boarding schools, broken into agencies, guardian services and exchange/student program sponsors — and lists the filter dimensions. It never states the listing verb outright and doesn't contrast itself with the singular sibling get_help_organization, so an agent must infer the list-vs-detail split from the tool name alone.

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?

Usage is implied by the enumeration of filter axes (kind, language, country, visa, state), which tells the agent this is the browsing/search path when no organization ID is known. However, there is no explicit when-to-use statement, no exclusion, and no pointer to get_help_organization or find_helpers as the alternative for a specific organization.

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