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

With no annotations provided, the description carries the transparency burden. It discloses important behavior: fields are null when no vendor endpoint exists and are 'never guessed', reported_success is null until 5+ distinct correlated reporters in 90 days, and there is an expected follow-up call to report_outcome. This is substantive, though it does not mention auth or read-only guarantees.

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 dense but front-loaded with the tool's purpose and placement in the buyer path. The long field lists are justified because there is no output schema, but the single-paragraph wall of text makes it slightly harder to scan than ideal.

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 there is no output schema, the description thoroughly documents return content, null semantics, the reported_success threshold, the required prior step, and the follow-up report_outcome call. An agent has enough context to select, invoke, and interpret results correctly.

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 coverage is 100%, and the sole parameter provider_id is already documented in the schema as the handle returned by search_providers or compare_providers. The description reinforces this provenance but adds no new semantic detail beyond what the schema provides, so baseline 3 is appropriate.

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 states a specific verb and resource: 'get full profile for ONE provider' and identifies the tool as 'Step 2 of the buyer path'. It also enumerates the exact content (plans, pricing model, liveness, evidence, how_to_connect), clearly distinguishing it from search_providers, compare_providers, and get_provider.

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 says to use this tool after search_providers returns handles, and instructs the agent to call report_outcome afterwards if the listing is used. This provides clear sequencing and context, though it does not explicitly list when-not-to-use alternatives like get_provider or compare_providers.

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