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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds real value beyond them: it discloses the cascade scope ('and every trade in it') and the authentication requirement (Authorization: Bearer <JWT>), neither of which is inferable from the structured fields.

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?

Three short sentences, front-loaded with the domain marker and the action, with zero filler. The bare 'PAPER.' fragment is terse to the point of being slightly cryptic, keeping this just below a 5.

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?

For a destructive, single-parameter tool with no output schema, the description covers the deletion scope and auth, which is reasonable. It omits whether the deletion is irreversible, what happens to any open positions tied to the ledger, and how the ledger is identified — gaps an agent would want before firing a destructive call.

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 single 'ledger' parameter has 0% schema description coverage, so the description must compensate. 'One of your paper ledgers' hints that the parameter selects which ledger, but gives no format detail (name vs. ID) or example, leaving the agent to guess how to populate it.

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 verb (deletes) and resource (a paper ledger plus every trade inside it), and the 'PAPER.' prefix scopes it to the paper-trading domain, separating it from live-trading siblings. An agent can distinguish it from signet_paper_buy/sell/positions without opening a schema.

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?

Use is implied by 'deletes one of your paper ledgers' — you call it when you want to clear a ledger — but there is no explicit when/when-not guidance and no reference to the related paper-trading siblings (buy, sell, positions) to route the agent away from them.

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