tiendanube_list_locations

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

With no annotations provided, the description carries full burden. It states 'retrieve' implying read-only, but lacks details on output format, pagination behavior, rate limits, or whether all locations are returned. Parameters like 'fields' and 'since_id' are unexplained, leaving behavioral gaps.

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 sentence, concise but too terse. The all-caps 'LIST LOCATIONS' adds noise. It front-loads the purpose but sacrifices detail. Could be split into two sentences for clarity.

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?

Given the tool has 8 parameters, no output schema, and no annotations, the description is insufficient. It does not explain parameter interactions (e.g., pagination with date filters), expected return data, or potential limits. A complete description would address these gaps.

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?

Schema description coverage is 0% for all 8 parameters. The description only vaguely references 'pagination and date filters', covering page, per_page, and date fields but omitting 'fields' and 'since_id'. This adds minimal value; the schema does not help, so the description should compensate but does not.

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 clearly states the verb 'Retrieve' and resource 'store locations', and mentions pagination and date filters, distinguishing it from sibling list tools that target different entities (orders, products, etc.). However, it does not explicitly differentiate from the singular get_location tool, though the plural 'locations' implies listing.

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 provides no guidance on when to use this tool versus alternatives like get_location for a specific location or other list tools. No context on prerequisites or appropriate scenarios (e.g., 'Use this to list all locations; use get_location for a single location').

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