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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds that the response includes product counts and a relatedGuides field for certain focused industries — useful return-shape context since no output schema exists — but says nothing about result size, ordering, or how counts are computed, so it only partially lifts the burden.

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 with no filler: the first front-loads what is returned, the second routes the agent to the alternative. The camelCase field name relatedGuides is the only mild stylistic wart, but it usefully pre-names a response key.

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 read-only list tool with no output schema, the description covers both what is listed and the key response contents (counts, relatedGuides). It stops short of describing granularity or breadth of the industry list, but nothing essential to invoking it correctly is missing.

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 takes zero parameters, so there is no parameter meaning for the description to add; the baseline for a parameterless tool applies. No schema gap is left unaddressed.

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?

Uses a specific verb ("List") plus resource ("industry affinities") and states what the result contains — product counts and relatedGuides for focused industries. The examples (veterinary practices, coffee roasters, galleries) make the domain concrete, and naming get_collection as the deeper-dive sibling lets an agent tell the two apart 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 routes detailed guidance to get_collection, which is a clear alternative. It does not state exclusions (e.g., when NOT to use this list) or whether it is the right entry point for browsing before drilling into a collection, but the context is clear enough to select correctly.

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