maltego_export_csv

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

The description discloses the output format and round-trip behavior, adding value beyond annotations. It also mentions the return value (confirmation with path and entity count). Annotations (idempotentHint=true, destructiveHint=true) are consistent with the description's implied behavior (exporting overwrites file, but is idempotent if graph unchanged).

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 clear paragraphs and structured Args/Returns sections. Every sentence serves a purpose, with the main action front-loaded. No redundant information.

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's simplicity (exporting to CSV), the description fully covers the purpose, format, parameter, and return value. The round-trip context and lack of output schema are adequately addressed.

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 description repeats the parameter 'path' from the input schema without adding new semantic detail. The schema itself already provides a description ('Destination file path for the export'). Therefore, the description does not significantly enhance parameter understanding beyond the schema.

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 specifies 'Export the active graph's entities to a CSV file', identifying the action (export), resource (active graph's entities), and format (CSV). It also mentions round-trip compatibility with import, distinguishing it from sibling export tools like maltego_export_json.

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 states that the exported CSV can be re-imported using maltego_import_csv, providing clear context for when to use this tool. However, it does not explicitly state when not to use it or mention alternatives like maltego_export_json.

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