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

The description reads as a pure retrieval, yet annotations declare readOnlyHint=false and idempotentHint=false, and the description offers no explanation of any side effect, logging, or state change that would justify that. It also says nothing about permissions, scoping, or result size/pagination for a 'full history' payload. With output_schema present the return shape is covered, but the non-read-only signal is left unexplained.

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?

A single front-loaded sentence fragment with zero filler. It is efficient, though the terseness edges into under-specification rather than disciplined brevity.

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 one-parameter read-shaped tool with an output schema, the return content is adequately signposted, but the missing sibling differentiation, usage conditions, and any hint about the non-read-only annotation leave real gaps. An agent knows what it gets back but not when to prefer it or what calling it may do.

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?

The schema has 0% description coverage on a single required agent_id, so the description must carry the meaning. 'for an agent' only loosely implies the identifier, but agent_id is self-explanatory by name, so the gap is small rather than harmful.

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 exact payload returned: full outcome history, attestation count, and current score for an agent. That is concrete, but it never distinguishes this tool from siblings like score_agent or describe_agent, which plausibly overlap on 'current score' and agent metadata, so an agent cannot route on the text alone.

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 or when-not-to-use guidance and no mention of the sibling alternatives. The agent must infer from the name 'history' that this is the audit-trail view versus score_agent for scoring or record_outcome for writing.

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