export_receipts_xlsx

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

Discloses return format (Base64-encoded XLSX) and input requirement. No annotations provided, so description covers essential behavior but lacks details on side effects or limitations.

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?

Very concise, purpose front-loaded, no redundant text. 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?

Sufficient for a simple export tool with one parameter. Covers what, input, and output. Could mention no side effects, but overall 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?

With 0% schema coverage, description compensates by explaining the parameter expects receipt extraction results from extract_receipt, adding semantic meaning beyond the raw 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?

Clearly states the tool exports receipt data as XLSX format. Differentiates from sibling export_receipts_csv by specifying Excel workbook format and links to extract_receipt as data source.

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?

Implies usage after extract_receipt by specifying input source. Does not explicitly compare with CSV export or state when not to use, but context is clear enough for simple export.

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