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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds useful behavioral context beyond annotations: the balance is pre-formatted with a currency symbol and the ledger includes the full set of transaction categories. No contradictions with annotations.

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?

A single, well-structured sentence packs the resource, return contents, formatting detail, and workspace scope without waste. The most important information is front-loaded.

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 parameterless read-only tool, the description fully specifies what the agent will receive: a formatted balance and a full ledger with transaction categories. Even without an output schema, no critical invocation or return semantics appear missing.

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 takes zero parameters, so the schema leaves nothing undocumented. The description still adds relevant context by scoping the result to the 'active workspace', which is the only implicit input the agent needs to understand.

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 clearly identifies the resource ('wallet') and the exact returned contents: 'total_credits, pre-formatted with currency symbol' and the 'full transaction ledger' including deposit, hold, charge, and release entries. It is unambiguous and conceptually distinct from siblings like get_account, though it does not explicitly name an alternative.

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 implies its use case: retrieve the active workspace's wallet balance and transaction history. However, it provides no explicit when-to-use guidance and does not differentiate it from similarly named or related tools such as get_account.

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