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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful operational detail (photos and PDFs, up to 50 at once), but 'exports the same files' is ambiguous about what the agent actually receives and whether the external site is involved in the flow, which sits awkwardly against openWorldHint=false. The added context is real but leaves the return behavior underspecified.

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?

A single dense sentence that front-loads the purpose and then layers the trigger condition and limits. Every clause carries information except the trailing 'and exports the same files,' which is vague enough to be close to 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 zero-parameter tool with no output schema, the description covers what it is, when to use it, and what it handles. The remaining gap is the return payload — whether the agent gets a URL, a handoff instruction, or something else — which matters because there is no output schema to fall back on.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The stated file-type and batch-size limits describe the tool's capacity, not parameter semantics.

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 states a specific resource ('InvoiceSnap's own scanner') and makes clear this tool hands back a link rather than performing OCR itself, which is the key distinction an agent needs. It does not name the siblings (build_receipt_spreadsheet, convert_currency), but their purposes are far enough apart that confusion is unlikely.

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?

It gives an explicit trigger condition: use it 'when receipt photos are hard to read or there are many.' That is clear routing guidance. It stops short of stating when not to use it (e.g. single clean receipt where an in-agent flow would suffice), so it is not a full 5.

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