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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely new context beyond them: SHADOW MODE means planned moves are paper records with no real capital movement, which is essential to interpret the payload correctly. It stops short of discussing auth, caching, or freshness of the snapshot.

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?

It is a single tightly packed paragraph that front-loads the resource and ends with the key SHADOW MODE caveat and endpoint pointers. Every clause maps to actual returned content, but the extreme density and unexplained jargon hurt scannability for a first-time reader.

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 effectively serves as one by enumerating the returned fields, and it adds the shadow-mode caveat plus related-endpoint pointers. It is largely complete, though the undefined domain terms leave an agent without full grounding on some field meanings.

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?

Zero parameters, so the baseline of 4 applies; there is nothing for the description to disambiguate. No parameter-level information is needed or missing.

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 precisely enumerates the resource returned (per-venue working-capital bands with under/band/over status, concentration flags, hedge reservations, planned rebalance moves, FX snapshot, logistics accounting), which is far more specific than the bare name/title. It also distinguishes itself from the fund/transfers endpoints that hold outcomes. However, the action itself is only implied via the title 'Read'; the body never states the verb outright, and the heavy jargon ('Thusus', 'arb-as-rebalance') assumes domain fluency.

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 draws a clear boundary: this endpoint returns the decision state, while live balances and the executed transfer log live at /arb/thusus/fund and /arb/thusus/transfers. That is an explicit alternative pointer, though there is no stated trigger for when an agent specifically needs the Quartermaster state versus those endpoints.

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