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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior, so safety needs no restating. The description adds one real behavioral fact: the payload bundles the provider's full offer set, which is useful. It says nothing about behavior for an unknown slug or how large the offer bundle may be.

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 short sentences with the payload content stated up front. The second sentence is vendor attribution rather than tool guidance, but it is brief and does not dilute the operational content.

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 one-parameter read with annotations covering the safety profile and no output schema, the description supplies the key missing piece: what comes back (provider plus all its offers). Gaps remain on unknown-slug behavior and on whether the single 'slug' field accepts a domain string.

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 0%, so the description must carry the parameter semantics, and it partially does by saying the lookup key can be a slug or a domain. That conflicts with the schema, which exposes a single field literally named 'slug' with a string type and no description, leaving format and domain handling ambiguous.

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 names a specific resource (provider) and what the response contains (every offer it sells), which is more than the title alone provides. It does not distinguish itself from siblings like r4ck_get_server or r4ck_list_providers, and 'here' is an ambiguous pointer rather than a concrete statement of what is returned.

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?

There is no when-to-use guidance, no exclusion of alternatives such as list_providers or search_servers, and no prerequisites stated. The only implied usage is 'look up one provider,' which the agent must infer from the name.

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