export_entries_csv

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

No annotations are provided, so the description carries the burden. It discloses the output format and columns, and implies a read operation (export). It does not mention permissions or side effects, but for a simple export, the behavior is reasonably transparent.

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 that efficiently conveys the core purpose and output columns. It is front-loaded and concise, though could be slightly more structured with separate lines for details.

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 no output schema, no annotations, and 2 parameters, the description is adequate but leaves gaps: it does not specify return values, error cases, or behavior when csv_path is null. For a simple tool, it is minimally 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 input schema has 2 parameters with 0% coverage in descriptions. The description does not explain what 'snapshot_path' or 'csv_path' mean, nor does it clarify optionality or defaults. Since schema coverage is low, the description should add meaning but fails to do so.

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 'Export', the resource 'snapshot's entries', the format 'CSV', and lists the specific columns (channel_id, author, etc.). It distinguishes itself from sibling tools like collect_entries by specifying the output format and purpose.

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 usage for exporting entries to CSV for spreadsheets, but does not provide explicit guidance on when to use this tool versus alternatives, or when not to use it. No exclusions or prerequisites are mentioned.

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