List Stores

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

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states 'Get all ecommerce stores' but does not mention return format, pagination, required permissions, or whether 'all' includes archived or inaccessible stores. This is minimal and leaves the agent guessing about important behavioral characteristics.

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 a single, clear sentence with no wasted words. It is front-loaded with the action and resource. For a simple tool with no parameters, this level of conciseness is well-optimized.

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?

The tool is low-complexity (no parameters, no output schema), and the description adequately states the primary purpose. However, without any detail about the return structure, result size, or potential errors, the description is only minimally viable. The lack of annotations and output schema increases the need for description to provide completeness, which it does not fully deliver.

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 there is nothing to explain. The description does not need to add parameter meaning, and the schema confirms no parameters exist. A baseline of 4 is appropriate for a parameterless 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?

The description 'Get all ecommerce stores' uses a specific verb ('Get') and resource ('ecommerce stores'), clearly distinguishing it from sibling tools like ecommerce_stores_create, ecommerce_stores_delete, and ecommerce_stores_metadata. The scope ('all') adds specificity.

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?

No guidance is provided on when to use this tool versus alternatives such as ecommerce_stores_metadata, which could also retrieve store-related information. The description lacks explicit context for selection, merely stating a basic action without contrasting with other list or read tools.

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