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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description contributes that the data is registry-observed and enumerates the content categories, but says nothing about pagination, time window, or volume limits for what could be a large history.

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?

Two sentences, no filler: the first states what is read and from where, the second states when to use it. Everything is front-loaded and 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?

With no output schema, the description usefully enumerates the returned content (counts, outcomes, counterparties, value, risk), which is the right compensation. It still omits any statement about history depth or whether the result is bounded, so it is strong but not fully complete.

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?

There is only one parameter and schema description coverage is 100% ('Agent identifier used in Economic Passports'), so the schema already carries the semantics. The description only implies the agent scoping ('for a specific autonomous agent') without adding format or source details, matching the baseline for high-coverage schemas.

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 gives a specific verb (read) and resource (economic history) scoped to a single autonomous agent and to data 'observed by this registry', which separates it from sibling operations like record_outcome or verify_economic_passport. It does not name a sibling directly, but the registry-scoped history framing is unambiguous.

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?

'Use when you need transaction counts, outcomes, counterparties, value, or current observed risk before deciding what to do' gives a concrete triggering situation and even the decision context. It stops short of naming an alternative tool (e.g. trust_before_action) or an exclusion, so it is clear context rather than full routing guidance.

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