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

With no annotations provided, the description must carry the transparency burden. It does disclose that a key is required and that a stored fingerprint is used, but it omits any mention of output format, error behavior, or rate limits. The read-only nature is implied but not explicitly stated.

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 brief and front-loaded, with the core purpose stated first and the auth pointer as a necessary second sentence. However, the first sentence is a grammatical fragment beginning with 'When' rather than a full declarative statement, which slightly hurts clarity.

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?

Given the lack of annotations and output schema, this description is incomplete. It does not explain the provider parameter, provide usage context versus siblings, or describe what value the tool returns. While the tool is simple, the description leaves notable gaps that an agent would need to resolve.

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 optional 'provider' string parameter with 0% description coverage, and the tool description never explains the parameter's format, allowed values, or how it maps to the stored fingerprint. The parameter name is self-explanatory to some degree, but the description adds no semantic value beyond the schema.

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 specifies the tool's purpose as reporting when a provider last changed its terms or pricing page, using a stored fingerprint. This clearly identifies the resource and distinguishes it from siblings like provider_incidents or model_price_history, though it lacks an explicit verb such as 'returns' or 'gets'.

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 guidance is given about when to use this tool versus alternatives like provider_transparency or provider_incidents. The only context provided is the key requirement, which is an authentication prerequisite rather than usage guidance.

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