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

Annotations already establish read-only, idempotent, open-world, and non-destructive behavior, so the description's additional 'privacy-safe' and 'historical' context earns some credit. However, it does not explain what data is consulted, how results are scoped, or what privacy guarantees mean in practice.

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?

One short sentence with no filler and the key behavior front-loaded. It is concise, though it could have used an extra clause to explain the hours parameter or expected result.

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 and an openWorldHint, the description leaves key invocation context unstated: what 'trust evidence' means, how the response is shaped, and what role hours plays. The annotations cover side-effect safety, but not enough for a confident call beyond the default arguments.

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 one parameter, hours, with 0% description coverage, and the description never mentions it. There is no explanation of how hours controls the lookup window or how it relates to 'historical', so the description fails to compensate for the schema gap.

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 a specific action and resource: it checks historical trust evidence, which distinguishes it from sibling tools that check identity, payment, or status. 'Privacy-safe' adds a qualifier, though 'trust evidence' remains somewhat generic.

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 about when to use this tool instead of check_identity, check_status, compare_providers, or verify_provider. The historical aspect is implied, but no explicit criteria or exclusions are given.

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