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 context beyond that: the data source ('independent artists' own shops') and the shape of the result (typical price, middle half of prices, price per square inch). It does not mention rate limits or latency, keeping it short of a 5.

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 sentences, front-loaded with the purpose, and the second sentence is dense but all content (source, three statistics, comparables) earns its place. Slightly heavy for the second sentence but no filler.

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?

There is no output schema, and the description compensates by naming the returned statistics (typical price, middle half, price per square inch) and the data source. Combined with full schema coverage and rich annotations, an agent has what it needs to call and interpret this tool; only explicit alternative-tool routing 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% with enums for kind and unit, so the schema already carries parameter meaning. The description restates the size/medium dimensions but adds no format, default, or edge-case detail beyond the schema (e.g. no note on unit defaults when omitted). 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+resource ('fair price for a new artwork') and scopes it by 'size and medium', which cleanly separates it from siblings like price_commission, calculate_resale_royalty, and compare_where_to_sell. An agent can identify the tool's output without opening the 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 word 'new' plus 'comparable works for sale' implies the pricing-a-fresh-work use case, but there is no explicit when-to-use/when-not guidance and no sibling is named as an alternative (e.g. price_commission for commissions, calculate_resale_royalty for resales). Usage is only implied.

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