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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: no sign-in required and tier-based result truncation (name/module/risk band only below Professional).

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 tight sentences: purpose/filters first, return fields second, access and tier caveat last. No filler; the only slight redundancy is echoing filter axes already in the schema.

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 headline fields (slug, name, module, score, risk_band, subtype) plus the tier-based truncation caveat. An agent has enough to call it correctly; pagination beyond 'limit' is the only unaddressed detail.

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 description coverage is 100% and all five parameters are documented in the schema including the risk_band enum values, so the baseline is 3. The description restates the same filter axes without adding format, defaults, or combination rules beyond what the schema already provides.

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 (Search) plus resource (providers with a current ACI Risk Indicator) and the available filter axes. It does not name a sibling to distinguish itself from, e.g. get_provider_detail or compare_providers, so it lands just short of a 5.

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?

Provides context (free-text and/or filter search) and access/no-sign-in info, but never states when to prefer this over get_provider_detail or compare_providers. Usage is implied by the verb 'search' rather than made explicit.

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