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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, and the description's "Read only" merely restates one of them. It does add genuine behavioral information about result scope (only products with an image and not yet banked), but says nothing about pagination or result volume, which matters for a list endpoint.

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?

A single front-loaded sentence that packs the resource, the filter predicate, the downstream consumer, and the safety profile with no filler. Nothing is wasted and nothing important is buried.

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 small read tool whose annotations cover safety and which needs no output schema explanation, the description conveys what the returned rows are. The gap is pagination semantics for limit/offset, which the description omits entirely and the schema only constrains numerically.

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 coverage is only 33%: site is documented but limit and offset carry no descriptions. The description never mentions paging, so it fails to compensate for the coverage gap on a third of the parameters, and the agent gets no guidance on how to page through candidates.

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 and resource and defines the candidate set precisely: the site's own catalogue products that already have an image and are not yet in the bank. That filter definition distinguishes it from list_products and get_product. The only wobble is that it routes to add_photo_from_product, which does not appear in the sibling tool list.

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?

"for add_photo_from_product" implies the workflow context, so the agent can infer it is a pre-step for adding a photo from a catalogue product. However, there is no explicit when-to-use, when-not-to-use, or comparison against list_products/list_photos/get_product, leaving the routing to inference.

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