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

Annotations already declare readOnly, idempotent, non-destructive behavior, so the bar is lower, and the description adds the non-obvious caveat that the returned record may not reflect current offerings or availability. That is genuine behavioral context beyond structured fields, though nothing is said about error behavior for unknown or stale ids.

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?

Two short sentences, the primary action and ID source first, the scope caveat second. No filler or restated annotation text.

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 single-parameter read with an output schema and full annotations, the description covers the essentials: where the id comes from and what the record does not guarantee. The only gap is what happens when the id does not resolve, which is minor given the output schema.

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?

With 0% schema description coverage, the description has to carry the weight, and it does: it identifies the parameter as a UUID and states its provenance (returned by search_providers). Format and pattern are still only in the schema, so it is not fully compensating.

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 gives a specific verb and resource ("Get the current provider record") and ties the input to a UUID from search_providers, which clearly separates it from the search tool. It does not distinguish itself from open_provider_explorer, so it stops short of a 5.

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?

It tells the agent where the id must come from (search_providers) and sets an explicit scope limit: it "does not verify current offerings or availability." That is clear usage context, though it does not name which sibling should be used when availability verification is needed.

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