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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered without the description. The description adds no behavioral context of its own — nothing about time range, pagination, result granularity, or whether history is bounded — and does not contradict the annotations.

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?

It is short with no padding, but the brevity is under-specification rather than economy; the '[trust]' category tag and title restatement occupy most of the available text. Nothing is front-loaded beyond a label.

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 tool with no output schema, the description should at least state what the history contains and how far back it goes. It says none of that, leaving the agent unable to predict the response shape or scope.

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 description coverage is 0% for the single required parameter agent_id, so the description must compensate and does not. It never says whether agent_id is the caller's own identity or an arbitrary agent, nor what format the identifier takes.

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 text "[trust] Trust score history" essentially restates the tool name and title; there is no verb (retrieve, list) and no statement of what a 'history' consists of. An agent can guess this returns past trust scores for an agent, but that inference comes from the name, not the description.

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 guidance on when to use this instead of trust_score, trust_decay, or agents_reputation, nor any prerequisites or exclusions. The description offers nothing to disambiguate among several closely related trust tools in the sibling list.

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