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

Annotations already declare readOnly, idempotent, openWorld and non-destructive behavior, so the safety profile is covered. The description adds useful dataset scope: geography (UK/US/CA), recurring nature, and fields such as entry fees and usual closing month. It does not say what an unfiltered call returns or how large the result set is.

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 short and front-loads the domain, but the opening brand line 'Art Spotter - Eye of the Beholder' carries no operational meaning. The second sentence is a comma-spliced fragment listing data attributes rather than a structured statement.

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 list tool with no output schema, no required params and fully documented schema fields, the description covers the domain adequately. It omits what happens with no filters, whether results are paginated, and whether closing dates are current or typical, which an agent calling it would benefit from knowing.

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 kind, media and country are already documented in the schema. The description corroborates country (UK, US, CA) and media examples but adds no filtering syntax or default behavior beyond the schema. 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?

The description clearly identifies the resource: recurring open calls, prizes, residencies and listing sites for artists in the UK, US and Canada. It is easy to distinguish from siblings like artspotter_search_art or artspotter_price_commission. It never uses an explicit verb such as 'list', relying on the tool name for that.

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 statement of when to use this tool versus alternatives, nor any prerequisites or exclusions. The filterable dimensions (kind, media, country) are only implied by the data description. An agent must infer the use case from the name alone.

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