get_hero_collections

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

As there are no annotations, the description must carry the burden. 'Fetch' indicates a read operation, and the mention of listId being used with list_products is a useful behavioral context. However, it doesn't specify authentication requirements, response format, or any side-effect guarantees, so it only partially discloses behavior.

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 concise sentences, front-loaded with the verb and resource. The second sentence provides actionable information about the listId-to-list_products workflow without redundancy.

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 simple, parameterless fetch tool with no output schema, the description provides the essential context: what it returns (hero collections), and how to use the returned listId to further browse products. It lacks details about return fields beyond listId and possible auth, but for the primary use case it is sufficiently 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?

The tool has zero parameters, so the description is not required to explain parameter semantics. The baseline of 4 applies because there's no parameter burden, and the description doesn't attempt to add unnecessary param information.

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 the specific verb 'Fetch' and resource 'homepage hero collections', clearly distinguishing it from siblings like get_flash_deals or list_products. It also provides a functional link to list_products via listId, making its role unambiguous.

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 implies a clear usage pattern: first retrieve hero collections, then pass the listId to list_products to browse products. It doesn't explicitly name exclusions or alternative tools for when not to use it, but the context is clear enough to guide an agent.

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