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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds useful scope about returned content (images, other colourways), but this overlaps with the output schema, and it says nothing about auth, rate limits, or freshness beyond what structured fields provide.

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 returned payload then the input requirement, with no wasted words. Slightly dense field enumeration but every element earns its place.

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 an output schema present, return values need not be re-explained, and the description still adds the url-sourcing detail an agent needs to invoke it correctly. Complete for a single-param detail tool; only lacks optional caveats like error handling for invalid paths.

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 0%, so the description must carry the burden for the single url param, and it does: it specifies the format ('site-relative product path') and its source field. This is genuinely additive over the bare string type in 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?

States a specific verb+resource ('Full Burberry product detail for one product page') and enumerates exactly what is returned. It clearly distinguishes itself from the burberry_search/burberry_category list tools by being the single-page detail fetcher.

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?

It tells the agent exactly where to obtain the required input ('url is the site-relative product path from burberry_search's or burberry_category's own products[].url field'), effectively routing from the sibling tools. It stops short of an explicit when-not-to-use statement, but the workflow context is unambiguous.

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