Shopping guide (read first)

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

With no annotations, the description states it 'returns the shopping playbook' but does not disclose potential side effects, permissions needed, or whether it's a live fetch. This is adequate but not detailed.

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 description is three sentences, efficient and to the point. It front-loads the key action and usage instruction. Slightly verbose due to listing contents, but acceptable.

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 tool with no parameters and no output schema, the description provides sufficient context: what the guide contains and when to use it. It does not describe the output format but is otherwise complete.

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?

There are no parameters; schema coverage is 100% trivially. Per the scoring guidelines for 0 parameters, baseline is 4. No additional parameter info is needed.

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 clearly specifies the tool returns the 'Ametller Origen shopping playbook' and outlines its contents (product presentation, cart management, reordering). It contrasts well with sibling tools that perform distinct actions like adding to cart or searching.

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?

Explicitly instructs to call this tool 'once at the start of any Ametller task' and before other actions like searching or adding to cart. However, it does not mention when not to use it or alternative tools.

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