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

The annotations already declare readOnlyHint=true and openWorldHint=true, so the bar is lower; the description adds genuine value by disclosing the hard 500-entry ranking ceiling and the page × per_page ≤ 500 constraint, plus the hint to narrow area/period/taxon to bring lower-ranked entries into reach. No contradiction with annotations is present.

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?

The description is dense but every sentence carries functional weight — purpose, kind semantics, area exclusivity, pagination ceiling, and sibling routing are all present and front-loaded. The em-dash flourish "who knows this place or this group" is mildly ornamental, but the overall structure is efficient for a tool with 15 parameters.

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?

Given the tool's high complexity — 15 parameters, cross-field exclusivity rules, and a pagination ceiling — the description covers the cross-parameter constraints an agent most needs to call it correctly: area-form exclusivity, page/per_page limits, and kind semantics. Minor caveats like the HTTP 500 on non-numeric place_id live only in the schema, and the output schema covers return values, so the description is reasonably complete.

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, but the description adds meaning beyond the schema: it synthesizes the mutually exclusive area forms (place_id vs lat/lng/radius vs bounding box), explains the pagination relationship between page and per_page, and clarifies what kind selects. This is genuine added value on top of the parameter-level schema descriptions.

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 names a specific verb and resource — "Rank the most active observers or identifiers for an area, period, and taxon" — and clarifies what each kind measures. It also distinguishes itself from the closest sibling tool, inaturalist_get_species_counts, so an agent can tell them apart without opening either schema.

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 explicitly routes the agent away from this tool toward inaturalist_get_species_counts when the goal is species frequency rather than person activity. It also gives clear context on when to use it (area, period, taxon) and how kind selects the ranking basis, though it does not address every potentially confusable sibling such as get_histogram.

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