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 two meaningful traits: the call is free and it requires the workspace key via _meta[satledger/api-key]. However, it says nothing about ordering, pagination, result size limits, or what the 'head hash' represents, which are real gaps for an unpaginated-looking list 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 short, front-loaded sentences with no filler: what it returns, what it costs, how to authenticate. Slight inefficiency in repeating the _meta auth detail already present in the schema, but overall tight.

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 list tool with no output schema and no annotations, the definition covers authentication and cost but leaves the return shape mostly unexplained beyond 'action log' and 'head hash'. An agent knows how to call it, but not what it will get back or whether results are complete/paginated.

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 (including the _meta preference), and the description's auth sentence largely restates that rather than adding new meaning. The required agent_id has no description anywhere, so half the parameters remain unexplained; the description neither compensates nor misleads.

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 identifies a specific resource (the agent's action log) and an extra piece of returned data (its head hash), which is enough to separate it from write-side siblings like record_action. It stops short of naming an alternative or stating the listing scope (all actions? recent?), so it is clear but not fully differentiated from siblings such as list_anchors.

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 when-to-use guidance: nothing says whether this should be called before/after record_action, whether it is the right tool versus list_anchors, or any precondition beyond authentication. The only contextual hint is the cost note ('Free'), which is useful but not usage guidance.

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