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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description still adds real value beyond that: it discloses pagination ('bounded pages'), a required scope, case-sensitive literal search semantics, and two caveats about interpretation ('storeNetwork describes the deployment, not per-run settlement'; 'Recorded spend/allocation is not a payment receipt').

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?

Compact and front-loaded: the purpose leads, followed by prerequisite and caveats, with no filler sentences. The telegraphic clause stacking ('No wallet selector, linked accounts, archive, private jobs, research or payment') hurts readability slightly but every clause carries information.

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?

Annotations are rich and there is no output schema to explain, so the remaining burden is parameter meaning and the description partly meets it. With 7 parameters at 0% schema coverage, the absence of any explanation for from/to, funding, and surface leaves an agent guessing at field semantics.

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 0% for 7 parameters, so the description carries the full burden. It clarifies pagination (limit/cursor) and search semantics ('literal case-sensitive'), but says nothing about from/to date behavior, the funding enum values, the surface enum values, or the 50-item limit. It even references a 'storeNetwork' concept that is not a parameter here.

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 bounded pages') and a scoped resource ('the verified API-key wallet's ordinary current-store runs'), and the trailing 'No wallet selector, linked accounts, archive, private jobs, research or payment' carves it away from the many history_* and research siblings. The jargon ('ordinary current-store runs') is opaque but the resource boundary is still discernible.

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?

'Requires explicit history:read' states a prerequisite, and the exclusion list clearly signals which adjacent scopes (archive, private jobs, research, payment) belong to other tools. It never names a specific sibling to route to, so the guidance is strong but stops short of explicit alternatives.

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