accesso_save_barcodes

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

The annotations declare readOnlyHint=true, but the description says the tool 'Writes PNGs' and writes to a filesystem, which is a side-effecting behavior. This directly contradicts the read-only annotation. The description is transparent about writing files, but the contradiction with the annotation is a serious inconsistency.

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?

The description is compact and efficient: it states the action, the default behavior, the alternative mode, and the key caveat in two sentences. There is no filler and the most important information is front-loaded.

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?

Despite having no output schema, the description explains what the tool returns in both modes ('paths' vs. 'the images directly'). It also covers the remote-server caveat and references the URL source, making it complete enough for an agent to invoke correctly.

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 coverage is 100%, so the schema already documents all three parameters. The description adds meaningful extra context about the inline mode being the only useful mode on remote servers, going slightly beyond the schema's parameter descriptions.

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 clearly states the action ('Save the scannable barcode images'), the resource ('from an accesso order'), and the output ('Writes PNGs and returns their paths'). It is specific enough to distinguish this from sibling tools that merely get orders or tickets.

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 gives clear context for choosing between default file-writing and inline mode, including the strong practical caveat that inline is the only useful mode on a remote server. It does not explicitly name sibling alternatives or say when not to use this tool, but the operational guidance is clear.

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