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

Annotations already declare readOnly, idempotent, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond that: the quote is signed, valid for only 15 minutes, tax-inclusive and priced in EUR, and non-negotiable, which materially affects how an agent should use it.

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?

Three short, front-loaded sentences with no filler. The most decision-relevant facts (price, validity, non-negotiability) come first and every sentence carries 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 read-only, no-output-schema tool whose safety profile is fully covered by annotations, the description is largely complete: it explains what is returned, the currency/tax basis, the signature, and the short validity window. The only real gap is guidance on the offer_id parameter and how the quote relates to the ordering flow.

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?

With only 50% schema coverage, the description should compensate but does not. 'One photograph' loosely suggests photo_id is the target photo, yet no format or identifier semantics are given, and the optional offer_id (licence unit selection) is never addressed in the description at all.

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 resource (fixed price plus licence terms for one photograph), so an agent knows this returns a quote for a single photo. It does not, however, distinguish itself from the sibling get_license, which also deals with licence terms, so sibling differentiation is absent.

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 such as get_license or get_photo. The statement 'Prices are not negotiable' is a constraint, not usage direction, so the agent must infer that this is a pre-purchase pricing step.

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