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

Goes well beyond the readOnly/non-destructive/openWorld annotations: nulls mean the vendor published nothing and 'nothing is guessed', deployment carries evidence, reported_success stays null until 5+ distinct reporters in 90 days, and price_applies_to flags prices belonging to the vendor's platform rather than the connector. This is uncommon, high-value disclosure about data trustworthiness and liveness.

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?

Front-loads the purpose before the field inventory, and every clause conveys a distinct return-value or trust signal rather than filler. The size is large but largely justified for a no-output-schema data tool, though the single run-on sentence is dense and slightly hard to parse.

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?

With no output schema, the description compensates by enumerating the returned fields (plans/prices with billing units, integrations, deployment, licence, connection methods, price_applies_to, product_group, reported_success) plus their null semantics. An agent knows both what it will get and when to trust it.

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 single provider_id parameter is fully documented as coming from search_providers or compare_providers, so the schema carries the load. The description adds no further meaning about the parameter beyond what the schema states, which is the correct baseline of 3.

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?

States a specific action (check one specific listing) and enumerates exactly what the profile contains (plans, prices, deployment, licence, connection methods), which clearly separates it from aggregate tools like search_providers and compare_providers. It does not, however, differentiate itself from the similarly named sibling get_provider, leaving ambiguity between the two.

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?

Gives concrete usage context: 'before recommending or connecting it' and routes follow-up action to report_outcome after actually using a listing. No explicit when-not or direct alternative is named (e.g. vs get_provider), so it stops short of full routing guidance.

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