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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, so the bar is lower. The description adds valuable context beyond annotations: the tool reports wallet, ledger, and gas status, and importantly that payouts fail closed on inconsistency, which is a meaningful behavioral consequence an agent should know.

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 two crisp sentences with no filler. The scope is front-loaded in the first sentence, and the second sentence earns its place by conveying the critical fail-closed behavior.

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?

The description gives a reasonable snapshot of purpose and one important behavior, but with no output schema it does not explain what the reconciliation response contains or how inconsistencies are reported. Auth prerequisites are present in the schema, so the description is minimally adequate but leaves the agent to guess at expected results.

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 description adds no meaning to either parameter. The schema already documents agent_key in detail, but admin_token is only constrained by minLength 16 with no explanation, and the description does not clarify how these auth parameters interact or when each is needed. With 50% schema coverage and no compensation in the description, parameter semantics are weak.

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 resource as an admin-only on-chain wallet, ledger, and gas status view, which distinguishes it from admin action tools like approve, pause, and kill_switch. It lacks an explicit verb such as 'retrieve' or 'list', but the intended purpose is clear enough for an agent to infer it is a status/read tool.

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 explicit when-to-use guidance and names no alternatives, despite many sibling admin tools. 'Admin-only' is an access constraint, not usage guidance; an agent cannot tell when to call reconciliation versus approve, disputes, or resolve_dispute without relying on the tool name alone.

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