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

With no annotations provided, the description carries the full burden, and it does well by disclosing the save location, supported formats, and Excel-specific formatting. It does not mention overwrite behavior or file naming, but overall it gives substantial behavioral context for a non-destructive export tool.

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?

Three short sentences each contribute unique information: action and destination, format list with semantics, and execution context with fallback instruction. The description is front-loaded and contains no filler.

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 tool with one optional parameter and an output schema, the description covers the operation effect, parameter meanings, and prerequisite workflow. Missing details like overwrite behavior and what happens when format is null are minor given the simplicity of the tool and the presence of structured schemas.

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%, but the description compensates by explaining each format value in plain language: excel as a table, zip as an archive with photos and files, and csv/json by name. It also adds useful detail about Excel numeric formatting. The only minor gap is the meaning of the default null, but the enum values themselves are well documented.

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?

Description uses a specific verb, saves collected cards to Downloads, and enumerates the supported formats. It clearly distinguishes itself from sibling tools like parsee_get_results and parsee_parse_urls by focusing on the export-to-file action and the last collection.

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 explicitly states that the tool operates on the last collection and instructs to call parsee_parse_urls first if no cards exist. This provides a concrete when-to-use condition and names the relevant alternative, which is exactly the guidance an agent needs.

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