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

No annotations are provided, so the description carries the burden. 'List' signals a read-only operation, and the description inventories the payload (counts, URLs, relatedGuides) plus the boundary that detailed guides live elsewhere. It does not mention pagination or response envelope, but for a zero-parameter list this is reasonably transparent.

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 focused sentences with no filler. The main purpose and output are front-loaded, followed by a useful sibling routing note.

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 zero-parameter tool with no output schema, it gives essential return expectations and points to get_collection for more detailed content. Minor ambiguity remains around the relationship between relatedGuides and detailed guides, but the overall behavior is well specified.

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, so the schema fully covers invocation. The description adds meaning by explaining what the result will contain, which is the relevant semantic context for this tool.

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 the specific action (List), the target resource (Shop by Intent curated collections), and the included output (counts, URLs, relatedGuides). It also distinguishes itself from get_collection by routing detailed guides there.

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?

Provides an explicit routing instruction: 'Use get_collection for those detailed guides.' It does not enumerate conditions for all sibling tools, but it clearly covers the closest alternative.

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