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

With no annotations, the description carries the full burden. It conveys that the tool returns a facet breakdown and mentions the context parameter's non-influence elsewhere, but it does not explicitly state read-only behavior, response format, or failure modes. For a simple get_ tool this is adequate but not fully transparent.

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?

Two sentences, zero wasted words. The core purpose and a concrete list of facets are front-loaded, and the explanatory contrast with the composite score is succinct.

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 tool with two parameters and no output schema, the description gives a solid overview of return content by enumerating the facets and mentioning regulatory regimes. However, it lacks explicit output structure, error behavior, or guidance for cases where no facets exist. Adequate for invocation, but not fully complete.

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?

The schema only describes the optional context parameter; slug is bare. The description ties slug to a specific provider, which adds meaning beyond the schema, but it provides no format or example for slug. The context parameter is already well-documented in the schema, so the description need not repeat it.

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 operation: take one provider's score and break it into named facets (discoverability, contract quality, governance, etc.), plus any applicable regulatory regime. This clearly differentiates the tool from composite-score siblings like get_provider_rating or 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?

The description provides clear context for when to use the tool: when the composite number is insufficient and a team needs the action-oriented breakdown. It implies a contrast with composite rating tools, but it does not explicitly name alternatives or state when not to use this tool.

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