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 disclose some behavior: newest-first ordering, a 200 cap on limit, and that matured claims carry text and salt. It omits, however, what 'matured' means, whether results are paginated, and whether tenant scoping has any auth implications.

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 short, front-loaded fragments with no filler. Slightly telegraphic and fragmented, but every sentence carries information and the ordering/limit facts come early.

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?

An output schema exists, so return values need not be explained. Still, for a read tool in a dense attestation family, the description lacks the sibling disambiguation and the definition of 'matured claims' an agent needs to call it confidently.

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%, so the description must compensate. It adds the meaningful constraint that limit tops out at 200, but the required tenant parameter is left entirely unexplained and 'matured' is not tied to any input. Partial compensation, not full.

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 (a tenant's sealed-claim stream) and its ordering, so an agent knows this lists attestation/claim data. However, it is phrased as a noun fragment rather than a verb+resource, and it never differentiates itself from close siblings like attestation_stats, attest_spec, attest_status, or list_reveals. The jargon 'sealed-claim stream' adds opacity rather than clarity.

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 statement of when to use this tool versus the many attestation-family siblings, no prerequisites, and no exclusions. The agent must infer usage purely from the name and content description.

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