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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds one real trait beyond that — results are catalog/provenance data, not live pricing or stock — but says nothing about pagination behavior, freshness of the catalog, or result ordering.

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?

A single front-loaded sentence led by the verb and resource, with no filler. Every clause carries information about scope or data provenance.

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?

An output schema exists so return values need not be explained, and annotations cover safety. However, the undocumented pagination/search parameters are a genuine gap for a list tool whose result set depends on limit/offset/search semantics.

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?

Three parameters (limit, offset, search) have 0% schema description coverage, and the description never mentions limit/offset paging or what the search string matches against. With no structured documentation and no compensating prose, the agent is left guessing what 'search' filters on.

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 (List) and resource (GPU compute services/providers), then scopes it as provenance metadata distinct from priced offers and live stock. This implicitly separates it from find_offers, though no sibling is named explicitly.

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 phrase 'independent of priced offers and live stock' hints at when this tool applies (catalog/provenance lookups rather than offer/availability queries), but there is no explicit when-to-use statement or named alternative. The agent must infer the routing from context.

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