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

With no annotations provided, the description carries the full burden and excels: it discloses that fields are null when the vendor publishes no endpoint ('never guessed'), explains the reported_success threshold (5+ distinct reporters in 90 days), and details the null behavior. This is rich behavioral detail beyond the schema.

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 long but dense and front-loaded with the purpose. Every sentence provides distinct value (field list, null policy, reported_success explanation, follow-up instruction). It is structured logically, though slightly sprawling.

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?

There is no output schema, so the description must convey return structure. It enumerates all major fields, explains the how_to_connect object, and covers edge cases like null endpoints and reported_success. This is fully complete for a one-parameter tool.

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 100% and the schema already states the provider_id is returned by search_providers or compare_providers. The tool description repeats this context but adds no new parameter-level meaning, so the baseline 3 applies.

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 uses a specific verb phrase ('drill into ONE provider') and clearly identifies the resource (a single provider profile). It also distinguishes itself from siblings by explicitly positioning it as a follow-up to search_providers or compare_providers.

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 explicitly states when to use the tool ('after search_providers or compare_providers') and provides a follow-up action ('call report_outcome afterwards'). However, it does not mention alternative tools like get_provider or specify when not to use it.

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