ePrinting balance and queue

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered structurally. The description adds only that the response combines two data sets (balance and queued jobs). It does not resolve the notable ambiguity of 'at a printer' when the schema has zero parameters – an agent cannot tell whether the printer is fixed by account config or whether the result spans printers.

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?

One short sentence with the two returned artifacts front-loaded and no filler. The only weakness is that its brevity leaves 'at a printer' unexplained rather than trimming genuine waste.

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?

With no output schema, the description carries the burden of describing return values and does so only at headline level – it never says whether the queue lists job names, sizes, or expiry, nor whether the balance is currency or pages. For a parameterless status tool this is minimally adequate but leaves an agent guessing at the payload shape.

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 zero parameters and 100% schema coverage there is nothing to document, so the baseline applies. The phrase 'at a printer' is the only wrinkle: it hints at printer scoping that has no corresponding parameter, which could momentarily confuse but does not misdescribe an actual input.

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 resource pair – the user's print balance and the jobs awaiting release – which is clearly distinct from the mutating siblings eprint_submit and eprint_cancel. It does not explicitly name those siblings, but the read-only 'status' framing makes the distinction inferable.

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?

There is no when-to-use guidance at all: nothing says to call this before eprint_submit, before eprint_cancel, or to check whether a job is stuck. Usage is only implied by the tool name, and no alternatives or exclusions are named despite three closely related eprint siblings.

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