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

No annotations are provided, so the description carries the full burden. It discloses that it resolves identifiers and returns selected groups, which suggests a read operation, but it does not explicitly state side-effect safety, error behavior, or the implications of the 'Understanding plan' note about the discovery layer. The context parameter's non-ranking behavior is documented in the schema, not the main description.

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?

The core value proposition is front-loaded and expressed compactly: 'One call, pick your field groups.' The final 'Understanding plan' sentence is cryptic and does not clearly earn its place, preventing a 5.

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 and no annotations, the description explains the selection model but not the shape or content of the returned groups, nor error behavior. An agent would need to infer those from sibling tools, so the description is adequate but incomplete.

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%, so the baseline is 3. The description adds a group list ('profile, onboarding, artifacts, rating, insights') but omits 'security', which the schema includes. This is a slight inconsistency rather than added meaning, and the default group set is already described in the schema.

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 precise function: 'resolves a slug OR any identifier and returns exactly the groups you ask for.' It lists the available groups and explicitly contrasts with chaining get_provider + get_provider_rating + get_provider_artifacts + get_provider_onboarding, clearly differentiating it from sibling tools.

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 directly positions the tool as a one-call alternative to chaining multiple get_provider* tools, which serves as a clear usage guideline. However, it does not state when not to use it (e.g., if only a single group is needed), so it lacks explicit exclusions.

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