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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is fully covered externally. The description adds what content categories are returned (UK arts council grants, Own Art 0% finance, ARR; US grants and group copyright), which is useful but offer no auth, rate-limit, or output-format context.

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 content is front-loaded and reasonably short, but the opening brand line and the title-restating sentence are redundant padding. The two country-specific sentences carry the real information.

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 single optional-parameter, read-only lookup with no output schema, the description conveys the topic, country coverage, and concrete examples. Annotations cover safety, so the remaining gap (return format) is minor and not required to call the tool 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 coverage is 100% with the country field documented as 'GB or US.', so a 3 would be the baseline. The description goes further by mapping each value to what it returns (UK institutions versus the US $85 group registration for 2-20 artworks), which genuinely helps the agent reason about the parameter.

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 the specific resource (grants, buyer finance, royalties, copyright for artists) and scopes it to UK and US schemes, so an agent understands this retrieves funding/copyright information. The first two sentences largely restate the title verbatim, but the country-specific content adds distinguishing detail versus siblings like artspotter_calculate_resale_royalty.

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?

There is no explicit when-to-use statement, no exclusions, and no sibling alternative named, despite calculate_resale_royalty covering an adjacent topic. The country breakdown implies the parameter choice but not when this tool should be selected over alternatives.

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