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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered structurally. The description adds some domain context — that prices carry a source and check date, hinting at data freshness — but says nothing about what happens when the name is unknown, or about rate limits and result size.

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 that states the lookup key first and the returned payload second. No filler, no restatement of the title.

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-only lookup with an output schema that already documents return shape, the description covers purpose and payload scope adequately. The only real gap is the slug-vs-id naming mismatch and the lack of not-found behavior, which are minor at this complexity.

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%, so the description must carry the parameter, and it does partially: 'by name or id (for example 'billit')' gives a concrete example. However, the parameter is named 'name_or_slug' while the description says 'name or id', an unresolved slug-vs-id ambiguity that leaves format expectations unclear.

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 resource (one tracked provider), the lookup key (name or id), and enumerates the returned content: capabilities, formats, languages, free plan, and prices with source and check date. That is far more specific than the bare name 'provider' and implicitly separates it from the sibling 'providers' list tool, though it never names that sibling explicitly.

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?

Usage is only implied: an agent can infer this is the per-entity lookup to use once it has a name or id, versus the 'providers' sibling for enumeration. No explicit when-to-use, when-not-to-use, or alternative routing statement is present.

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