list_export_locations

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

The verb 'List' implies a safe, read-only operation, which is a behavioral trait. Yet with no annotations and no output schema, the description provides no details about return format, pagination, or permissions, leaving the agent to infer behavior from the name.

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, entirely meaningful sentence with no wasted words. It is front-loaded and appropriately sized for a zero-parameter list operation.

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 zero-parameter list tool with no output schema, the description is largely complete: it tells the agent what the operation returns (a list of export locations). Minor gaps like the exact shape of each location item are inferable from sibling tools such as get_export_location.

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 baseline is 4. The description does not need to explain parameter semantics, and the empty schema confirms no arguments are required.

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 a specific verb ('List') and resource ('configured export locations'), and the word 'all' distinguishes it from the singular sibling get_export_location. However, it does not explicitly differentiate from other list_* tools, making it clear but not fully distinguishing.

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?

Usage is implied by the description: an agent would use this when needing a list of all export locations. However, there is no explicit guidance on when to prefer this over alternatives like get_export_location, nor any mention of exclusions or prerequisites.

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