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

With no annotations, the description carries the full burden. It does disclose two genuinely useful behaviors – the call is free and it requires workspace-key authentication via _meta[satledger/api-key] – but says nothing about read-only safety, result volume, or pagination behavior for what looks like an unbounded list.

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 sentences with no filler, and the first sentence front-loads what the tool returns. The opening fragment lacks a verb, which slightly blunts immediate comprehension, but nothing is padded.

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 two-parameter read tool with no output schema and no annotations, the description covers purpose, cost, and auth, which is the minimum viable set. It leaves gaps on ordering, result limits, and whether an unrecognized agent_id fails or returns empty.

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 50%: api_key is documented in the schema, agent_id only has a pattern. The description reinforces the auth mechanism and implicitly defines agent_id as the agent whose commitments are listed, which partially compensates but adds little beyond the schema text.

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 states the resource precisely – every anchor commitment recorded for a given agent – which reads clearly as a retrieval operation. It does not explicitly contrast itself with the sibling anchor_agent (which presumably creates anchors), so an agent must infer the read-vs-write split.

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 implied: call this to retrieve an agent's anchor commitments. The 'Free' note is a useful selection hint, but no alternatives are named and no when-not condition is given, so the agent gets context without explicit routing.

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