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

With no annotations, the description carries the full burden and does disclose key side effects: it 'Creates Item(s) and queues extraction', and it explains the misrouting behavior. It stops short of stating permission requirements, whether uploads are idempotent, or limits on file size/count.

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?

Front-loads the purpose and accepted types, then the routing warning in a clearly marked final paragraph. Slightly verbose around the backtick-quoted parameter names, but no sentence is wasted.

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 0%-coverage, no-annotation, no-output-schema mutation tool, the purpose and routing story are complete, but gaps remain: two parameters are undefined and no auth/idempotency behavior is given. Adequate but not fully self-contained.

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%, so the description must compensate. It usefully defines file_base64 (raw bytes, base64-encoded) and direction (payable vs receivable), covering two of four parameters, but leaves filename and company_id undocumented in both the schema and the description.

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?

States a specific verb and resource ('Upload an INVOICE or RECEIPT ... for analysis') and immediately scopes the file types accepted (PDF, image, .zip). It also explicitly distinguishes itself from the sibling upload_intake, so an agent can route without inspecting either schema.

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?

Gives an explicit when-not: 'For anything that is not an invoice — or when you are not sure what the file is — use upload_intake.' It also describes the consequence of misrouting (file is analysed and sits as a document), which is exactly the decision support an agent needs.

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