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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety is covered. The description adds genuine value by enumerating the response contents (deposit, revision rounds, cancellation fees, copyright, contract checklist), which tells the agent what the guide actually covers. No auth, rate-limit or freshness caveats are given.

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 purpose and sizing/level inputs are front-loaded in the first two sentences. The final sentence is an undifferentiated laundry list of covered topics, which is informative but slightly padded rather than tightly written.

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 and all five parameters documented, the description usefully enumerates the expected return content so the agent knows what answers are possible. It is nearly complete for a read-only lookup tool, missing only selection guidance against the neighboring price tools.

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% with clear enum and unit docs, so the schema carries the burden. The description only loosely echoes two parameters ('by size and the artist's level') without adding format or interaction detail beyond what the schema already states, so baseline 3 applies.

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+resource ('a price guide for a commissioned piece by size and the artist's level') and the exact scope of what it returns. It is clearly distinct in topic from siblings like artspotter_get_fair_art_price or artspotter_calculate_resale_royalty, though it never names an alternative to differentiate explicitly.

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 content ('commissioning a piece'), so an agent can infer this is for pre-commission pricing queries. However, there is no explicit when-to-use trigger or when-not guidance, and no routing away from the similar-sounding get_fair_art_price sibling.

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