list_exports

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

With no annotations provided, the description must carry the behavioral burden. 'List' conveys a read-only operation and 'with row counts' discloses a useful output trait. However, it doesn't explain behavioral details such as whether 'contains' filters results, whether the list is ordered, or what happens when no exports match.

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 short sentences with no filler. The core purpose is front-loaded, and the usage guidance earns its place by routing the agent to read_export. Nothing redundant is present.

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 list operation this is reasonably complete, but the lack of an output schema and annotations means the description should clarify the return format and the 'contains' parameter. It covers the main ask but leaves moderate gaps for a correctly informed call.

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%, so the description must add meaning to parameters. It connects 'crawl' to a crawl folder, but 'contains' is left entirely undocumented; an agent must infer that it might filter by name or content. This is insufficient compensation for zero schema-level descriptions.

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 action ('List the CSV exports'), the resource ('in a crawl folder'), and a notable output detail ('with row counts'). It also immediately contrasts with read_export by framing this as the discovery step before reading, so an agent can distinguish it from siblings.

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 gives explicit usage context: 'Use this to find the right export before calling read_export.' This tells the agent when to use the tool and sets up the expected sequence. It does not list when-not-to-use conditions or alternative tools beyond read_export, so it stops short of a full 5.

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