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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful scope by enumerating the kinds of outputs returned (deposit, revision rounds, cancellation fees, copyright, contract checklist). It stops short of stating that figures are estimates, whether results depend on external data, or any caveats, so it only modestly exceeds the annotation baseline.

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 first sentence is a verbatim restatement of the title and is pure waste. The second sentence is a long but informative enumerations of outputs, and the key scope ('by size and the artist's level') is not front-loaded. Readable, but not tight.

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, the description compensates well by listing the returned content (price guide, comparable sales, deposit, revision rounds, cancellation fees, copyright, contract checklist). Parameters are fully covered by the schema. The remaining gap is the lack of disambiguation from pricing siblings, which matters in this crowded sibling set.

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 width, height, unit, level and medium are fully documented in the schema, giving a baseline of 3. The description only loosely mirrors two of them ('by size and the artist's level') without adding format, default, or range detail, so it adds little beyond the schema.

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 states a specific resource and function: a price guide plus terms (deposit, revision rounds, cancellation fees, copyright, contract checklist) for a commissioned piece, scoped by size and artist level. It is far more informative than the title alone. It does not, however, differentiate itself from siblings like get_fair_art_price or calculate_resale_royalty, so an agent must infer the boundary.

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 guidance and no mention of alternatives, despite the sibling set containing several pricing-related tools. The commissioning context is implied only by the word 'commissioning,' which is not enough to route reliably between get_fair_art_price and this tool.

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