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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile and open-world nature are already covered. The description adds the intent semantics (related vs complementary) and the limit cap, but says nothing about pagination, ranking rationale, or whether an unknown handle errors. With annotations carrying the safety burden, a 3 is appropriate.

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 tight sentence front-loads the verb and resource, then appends the routing information. No wasted words, and the guidance sentence 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 described, and the description plus annotations and 100% schema coverage give an agent what it needs to call the tool correctly. Minor gaps remain around error behavior and recommendation ordering, but the core is 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?

Schema description coverage is 100%, with limit default/max and intent enum values fully documented in the schema. The description restates intent and limit without adding format or syntax beyond the structured fields, so baseline 3 is correct.

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?

Specific verb 'fetch recommended product items' plus a precise resource scope ('for one Everlane seed product handle'). It also disambiguates against siblings by naming everlane_product, everlane_products and everlane_collection_products, so an agent can separate recommendation lookup from product lookup without opening schemas.

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 tells the agent how to obtain the required seed handle and routes it to the alternatives, everlane_product/everlane_products for a handle and everlane_collection_products for a collection. This is when-to-use guidance with named alternatives.

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