export_crawl

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

Annotations indicate readOnlyHint=false (mutation) and destructiveHint=false, which the description supports by describing a non-destructive data export. The description adds that CSV files are generated, returns an export_id, and directs to read_crawl_data for reading. It does not disclose rate limits or auth, but the annotations already cover safety.

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 well-structured with Args and Returns sections, front-loaded with the main purpose. It is reasonably concise, though the default value for export_tabs is lengthy. Still, every sentence adds value.

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 presence of an output schema, the description need not detail return values, but it does and also mentions the follow-up tool read_crawl_data. It covers key aspects: export, returned IDs, and next steps. It is complete for a data export tool.

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 coverage is 0%, so the description must compensate. It does so effectively: explains db_id source, lists defaults for export_tabs with reference, gives examples for bulk_export and save_report. This adds substantial meaning beyond the bare schema property names.

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 action: 'Load a saved crawl from SF's database and export data as CSV files.' It uses a specific verb ('export') and identifies the resource (saved crawl) and output format. This distinctively separates it from siblings like 'crawl_site' (create) and 'read_crawl_data' (read exported data).

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 use after a crawl is completed, and it directs users to the 'export-reference resource' for options. However, it lacks explicit when-to-use or when-not-to-use guidance, nor does it mention alternatives among siblings. It provides clear context but no exclusions.

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