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

With no annotations, the description carries the full burden and does real work: it discloses that non-listable slugs return null rather than erroring, enumerates the returned content, and disclaims recommendation scope. It stops short of stating permission requirements, rate limits, or whether the fee is a snapshot vs. live value.

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 verb and resource, then the return payload, then two short caveats about null and scope. Every clause earns its place; the only minor cost is that the field enumeration makes the opening sentence long.

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?

No output schema exists, so the description usefully lists the return fields and the null case, which is what an agent needs to decide whether the response is usable. Remaining gaps (shape of 'locations' and 'treatments', currency of the fee) are minor for a single-parameter lookup.

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 0% for the single 'slug' parameter, so the description must compensate. It does so partially by tying slug to a registered provider identity and by explaining the null outcome for unlistable slugs, but it adds no format, case-sensitivity, or sourcing guidance for obtaining a valid slug.

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 ('Get one registered provider') and then enumerates exactly what comes back: registration wording and rating, treatments, locations, and published consultation fee. The 'by its slug' phrasing implicitly separates it from providers_search, but neither that sibling nor providers_check is named, so differentiation is inferred rather than stated.

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 slug-based lookup framing implies this is the tool to use when an identifier is already known, and 'Registration facts only, no recommendation' sets a scope boundary. However, it never explicitly says when to prefer this over providers_search or providers_check, nor does it state prerequisites such as needing a slug obtained elsewhere.

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