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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds useful behavioral detail about what the agent gets back (a top sample plus the total) and the existence of a 'next' affordance block in later sentences of the schema. It does not restate or contradict the annotations.

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 tightly packed sentences with the payload description front-loaded and the routing advice second. No filler, and the most decision-relevant information (alternative tool and view switch) is visible immediately.

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 entity lookup with a 100%-documented schema and no output schema, the description tells the agent what entity it returns, what the member payload is (a sample with a total), and where to go for the full list. Nothing needed to call it correctly is missing.

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 slug, view, limit, context, and include_next are all documented in the schema. The description only echoes view=full and the sample/total notion, adding little meaning beyond the structured fields; baseline 3 is appropriate.

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 and resource ('One country: metadata, counts, and a top sample of member providers') and even scopes the payload shape (sample + total). It differentiates from find_providers by contrast, though it does not address overlap with get_country_leaders or find_countries as a discovery path.

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?

Explicitly routes the agent: 'Use find_providers?country=slug for the full ranked list, or view=full here' gives a named alternative plus the parameter-switch condition. It lacks an explicit exclusion (e.g., when not to use this in favor of get_country_leaders), so it is clear context rather than full when/when-not coverage.

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