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

With no annotations provided, the description carries the full behavioral burden and delivers: it discloses plan gating (Understanding plan vs free), evidence sourcing behavior (from its own contracts rather than marketing), and the output structure (capability rollup with tag-level evidence under each). It stops short of return-format details or entitlement/error behavior, but the meaningful behavioral traits are present.

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?

Three compact sentences, front-loaded with the core purpose and arranged so the scoping and the sibling distinction land naturally at the end. Every sentence earns its place: the plan indicator, the purpose, and the routing note are all load-bearing.

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 low-complexity tool (2 params, no output schema, no annotations), the description is nearly complete: it conveys scope, plan implications, evidence sourcing, and an overview of the return shape. Minor gaps remain — no explicit note on the response as a data structure or what happens when the Understanding plan is unavailable — but the essentials for selecting and invoking it are covered.

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 50%: the optional context parameter is well documented in the schema, while slug has no description. The description partially compensates by implying slug identifies the vendor ('ONE vendor's published APIs'), but it adds no format, examples, or accepted-value guidance for slug. Adequate but not rich.

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 precisely what the tool returns: ONE vendor's published business capabilities, rolled up by capability with tag-level evidence, sourced from its own contracts rather than marketing. The explicit contrast with the get_provider_capabilities sibling disambiguates it without opening either schema.

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 names the exact alternative (get_provider_capabilities) and the distinguishing conditions: artifact counts and agent-readiness dimensions on the free side vs. business capabilities from contracts on the Understanding plan side. The phrase 'Answers what is this vendor actually for' gives the agent a clear trigger condition for choosing this tool.

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