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

Annotations already declare readOnly=true and destructive=false, so the safety profile is covered. The description adds non-annotation context: the required permission scope (orders:read) and the account/MCP-key prerequisite, which are real behavioral constraints. It doesn't disclose pagination or rate-limit behavior, keeping it short of a 5.

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 compact sentences with no filler; the resource and its contents are front-loaded before the permission and prerequisite parentheticals. Minor density from stacked brackets but still efficient.

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 read-only list tool with no output schema, the description usefully names the returned contents (items, payment reference) and the permission needed. However, with no output schema and an undocumented 'limit' parameter, it omits how results are paged or capped, leaving a modest gap.

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% for the lone 'limit' parameter, so the schema only gives bounds and a default without meaning. The description never mentions 'limit' or how pagination/result capping works, failing to compensate for the coverage gap.

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?

Names a specific verb and resource ('Orders of the account') and clarifies scope with 'checkout and renewals', plus what each order carries (items, payment reference). It distinguishes itself from gpucloud_get_order implicitly via the plural list framing, but never names the sibling 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?

Usage is only implied by the 'list' verb; there is no explicit when-to-use or when-not guidance, and no contrast with gpucloud_get_order, gpucloud_create_order, or gpucloud_list_invoices. The permission note ('orders:read') hints at the caller context but does not route between alternatives.

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