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

Annotations cover the safety profile (readOnly, non-destructive, closed-world), and the description adds substantial context beyond them: the ranking basis, the fields each result carries (price, liveness, upvotes, how_to_connect, deployment), and the important caveat about empty cheaper_only responses. This is genuinely useful behavioral disclosure.

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-loaded with the core purpose and ranking basis, and every sentence carries information. It is dense to the point of being run-on, with heavy parenthetical asides and a slightly redundant second mention of how_to_connect, minor costs against otherwise tight structure.

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 carries the burden of describing return values and does so (price, endpoint liveness, upvotes, how_to_connect, deployment, install/repository). Combined with the cheaper_only caveat, an agent has enough to 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%, so the baseline is 3, and the schema already documents limit and cheaper_only thoroughly. The description adds the alias mapping for agent_id ('aliases: handle, id'), which is meaning beyond the schema, plus elaboration on cheaper_only's comparison semantics.

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 verb and resource ('Find related alternatives to a known provider') and explains the ranking mechanism (embedding nearness to the provider's own profile, explicitly NOT category lookup). It also distinguishes itself from siblings compare_providers and research_capability, which surface the same substitutes in a different context.

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?

Explains that substitutes are also surfaced inside research_capability and compare_providers and gives interpretation guidance for cheaper_only (empty responses may mean a missing/incompatible reference price, not absence of alternatives). It lacks an explicit 'use this when / not when' statement versus those siblings, so the routing decision is still partly inferential.

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