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

Annotations declare readOnlyHint=true and destructiveHint=false, and the description adds genuinely new context beyond them: a required Authorization: Bearer <JWT> credential and the fact that open positions are marked at a live Jupiter quote (implying an external quote fetch with possible transient failures). It does not cover rate limits or behavior when quotes are unavailable.

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 dense sentence that front-loads the mode marker and enumerates the returned payload compactly. Nothing is wasted, though the parenthetical field lists make it slightly list-heavy rather than prose.

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 sensibly enumerates return contents (entry, cost, mark, unrealized, realized, counts, win rate) and states the auth requirement, which is adequate for a read tool. The unexplained 'ledger' parameter and absence of any error/empty-state behavior leave a real gap.

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 and is optional, so the description carries the burden of explaining it — but it never mentions the parameter at all, leaving the agent unable to know what values select which ledger.

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 names the resource precisely (paper ledger: open positions, closed trades, totals) and enumerates the fields returned, so an agent knows this is a read of the paper-trading book rather than a mutation like signet_paper_buy or signet_paper_sell. The verb is implicit (retrieve/show) rather than stated, and it doesn't explicitly contrast with signet_portfolio.

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 or when-not-to-use statement. The 'PAPER' marker implies paper-trading mode, but the description never tells the agent how this differs from the sibling signet_portfolio or when to prefer this over that tool.

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