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

Annotations already declare readOnly/idempotent/non-destructive, and the description still adds real value beyond them: required credential scope, the claimed-workspace requirement with the specific 403 failure mode for self-registered sandbox keys, and the newest-first ordering of results. Those are exactly the operational traits an agent cannot infer from 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?

The return payload is front-loaded in the first sentence and the prerequisites follow, so the agent gets the core purpose immediately. The enumeration of window counts is a touch long, but each clause maps to a distinct piece of returned data rather than filler.

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 usefully enumerates what comes back (settings, terms, counts, refund total, window list) and covers auth and workspace-claim failure modes. It does not mention pagination behavior beyond the limit cap, a small gap for a list tool that could return up to 200 windows.

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?

Schema coverage is 100%, so limit (default 50, max 200) and the open/decided status enum are already fully documented. The description adds only the ordering ('newest first') and clarifies that accepted/rejected windows are subsets of the decided status, which is a marginal gain over the schema baseline.

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 (read) and resource (workspace outcome pricing) and enumerates the returned content: on/off flag, terms, counts of open/accepted/rejected windows, total refunded, and the windows themselves. That distinguishes it cleanly from the mutating sibling report_outcome without needing to open either 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?

Gives concrete preconditions — a Last Price credential with price compute scope, and a claimed workspace (sandbox keys get 403) — which tells the agent exactly when the call will fail. It does not name an explicit alternative or exclusion (e.g., report_outcome for writing outcomes), so it stops short of full routing guidance.

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