Upload Voucher File

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

Description provides basic behavior ('upload') but does not disclose details like overwrite behavior, file size limits, or side effects beyond what annotations indicate (readOnlyHint=false, destructiveHint=false). Annotations partly cover safety but description adds minimal extra context.

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?

Single-sentence description is concise and front-loaded, but lacks some behavioral details. Could be slightly more informative without losing brevity.

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?

No output schema, so description should explain return behavior or confirmation. It does not mention response format, error conditions, or file size limits. Adequate but incomplete for a mutation tool with 4 parameters.

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?

All four parameters have descriptions in the schema (100% coverage), so the description adds no extra meaning beyond documenting parameters like id, fileName, contentBase64, contentType. Baseline 3 is appropriate.

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 clearly states 'Upload a file attachment to a bookkeeping voucher,' specifying the action and resource. It effectively distinguishes from sibling tools like lexware_upload_file (generic upload) and lexware_download_file (download).

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?

No guidance on when to use this tool over alternatives such as lexware_upload_file or when a voucher must exist. Lacks context for appropriate usage.

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