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

The description explicitly claims 'Writes nothing,' which contradicts the readOnlyHint=false annotation. No other behavioral context (auth, side effects, failure modes) is supplied, so the description misleads rather than clarifies the tool's behavior.

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 main sentence is compact and packs the essential output list into one line. The trailing 'Pro.' is unexplained noise and 'Work out what puts the float back to its imprest' is slightly indirect, but the overall definition is small and readable.

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 only two optional, fully documented parameters, the description gives the core computation and states safety ('Writes nothing'). However, it lacks an output schema and does not describe the actual return shape or error behavior, and the 'Pro.' flag adds ambiguity.

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 100%: both date and float already have descriptive meanings in the schema. The description adds nothing about how date or float affect the computation, so it meets but does not exceed the baseline.

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 identifies the operation as computing a replenishment: 'the amount, the vouchers it reimburses, the totals per category as an expense_add-ready payload, and the double entry.' This goes beyond the title by naming concrete outputs, though it does not explicitly distinguish the tool from siblings such as topup_record or reconcile.

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 no when-to-use guidance, exclusions, or alternatives. 'Writes nothing' hints at preview-only use, but the tool never says to use this before topup_record or instead of reconcile, so an agent must infer the intended workflow.

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