export_review_csv

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

With annotations (readOnlyHint=false) indicating potential side effects, the description fails to clarify if the export modifies any state or where the CSV is stored. It adds minimal context beyond the annotations, leaving behavioral ambiguity.

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 concise with two sentences, no redundant information, and straightforward structure. Every word adds value to understanding the workflow.

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?

While the description outlines the export-edit-reimport workflow, it lacks details on the CSV output format (beyond the decision column) and parameter semantics. Given no output schema, these gaps reduce completeness.

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 sole parameter 'path' has no description in the schema and the description does not explain what it represents (e.g., local file path, output directory). With 0% schema coverage, 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 tool exports all sender groups to a CSV for spreadsheet review, and distinguishes from the sibling import_review_csv by mentioning the re-import step. However, it could be more specific about the CSV's columns beyond the decision column.

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 reviewing and editing decisions via the re-import workflow, but does not explicitly state when to use this tool versus alternatives like get_sender_detail or set_decisions. No exclusions or when-not-to-use guidance provided.

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