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

Annotations already declare readOnlyHint=true and destructiveHint=false, which match the verb 'Read.' The description adds mild context by saying the history is 'portable' and 'verified' and scoped 'for an agent,' but it does not define what portability/verification mean in the output. This is adequate given the annotation coverage.

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?

The description is one tight sentence that front-loads the verb and object, with no redundant phrases. It is compact, though slightly under-specified.

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 should indicate what the tool returns, such as the shape or level of detail of 'economic history.' It also does not mention error/authorization conditions or how 'portable' manifests in the response, so an agent cannot fully anticipate the invocation result.

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 0% and there is one agentId parameter. The phrase 'for an agent' only loosely explains that agentId refers to the subject of the history; it does not clarify ID format, whether it must be the caller's ID, or how the value is used. The description does not fully compensate for missing schema documentation.

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 uses the verb 'Read' and names a specific resource, 'portable verified economic history for an agent,' which goes beyond the title and distinguishes the tool from offer/metrics siblings. 'Portable verified' is somewhat opaque but the core purpose is clear.

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?

No when-to-use or when-not-to-use guidance is provided. The description never contrasts this tool with related read tools such as get_network_metrics, get_verified_offer, or verify_portable_bundle, so an agent cannot decide between them from the description alone.

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