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

With no annotations, the description carries the full burden, and it does add meaningful epistemic caveats: declarations are wallet-signed self-declarations that do not prove the model executed the work, and older transactions without snapshots are unknown. However, it never states that this is a read-only operation, describes pagination behavior or defaults, or says what the returned records look like. Useful trust context, but incomplete disclosure for an unannotated tool.

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 sentences with no filler, and the purpose statement is front-loaded before the caveats. Each caveat sentence adds real information about data trustworthiness rather than restating the title. Slightly dense wording ('at claim and delivery submission') costs a point.

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?

No output schema and no annotations mean the description must cover return shape and safety profile, and it does neither. Combined with zero parameter documentation for four params, an agent cannot determine what a page of results contains or how to size it. The caveats are valuable but do not fill the structural gaps.

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 description coverage is 0% across four parameters, so the description would need to compensate and does not. 'Page' faintly implies limit/offset, and 'transaction snapshots' hints at the transactions flag, but address, limit bounds, offset paging, and the transactions toggle are never explained. An agent must read the raw schema to use any parameter correctly.

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 opens with a concrete verb and resource: paging an agent's immutable declaration history or transaction snapshots. It is distinguishable from reads like agent_profile or explore_history in substance, though it never names a sibling or explicitly contrasts itself with them. The phrase 'at claim and delivery submission' is somewhat cryptic but does narrow the scope.

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?

Usage is only implied: an agent can infer it should call this when it wants an agent's declaration or snapshot history. There is no statement of when to prefer this over explore_history or agent_profile, and no prerequisites or exclusions are given. The reader must infer the call condition from the resource description.

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