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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the output includes product counts and relatedGuides, and the verb 'List' implies a read-only operation. It does not mention pagination, authentication, or any exact return structure, which are minor gaps for a simple zero-parameter tool.

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 two sentences with no wasted wording. The first sentence delivers the core function and content, and the second sentence points to an alternative. It is front-loaded and easy to scan.

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, no-output-schema tool, the description explains the main return content: industry affinities, product counts, and relatedGuides for focused industries. It is mostly complete, though the exact shape or scope of 'relatedGuides' could be slightly clearer.

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?

The tool has zero parameters and the schema coverage is 100%, so the schema fully documents everything needed. The description adds no parameter-specific information, but none is required, making the baseline 4 appropriate.

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 uses a specific verb-resource pair: 'List industry affinities with product counts, plus relatedGuides for focused industries.' It clearly identifies what the tool returns. It mentions get_collection as a related alternative, but does not distinguish it from other sibling tools like get_categories or get_brands.

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?

The description gives explicit guidance to 'Use get_collection for detailed guidance,' which helps an agent decide when to prefer this tool over one alternative. However, it does not provide broader when-to-use or when-not-to-use context relative to the many other sibling tools.

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