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

Annotations already declare readOnly, idempotent, non-destructive, open-world. The description adds meaningful behavioral detail beyond that: the pagination contract ('If has_more is true, call again with page = next_page'), referencing response fields not exposed in any output schema. Useful, but no mention of ordering, result caps, or default scope richness.

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?

Four tight sentences, front-loaded with purpose then usage then the operational pagination tip. Every sentence carries weight; there is no filler or repetition of 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?

For a read-only list tool whose annotations cover the safety profile and with no output schema, the description covers purpose, filtering, and pagination adequately. It could say more about return shape or default result caps, but nothing critical for correct invocation is missing.

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 coverage is 100%, so every parameter (page, limit, state, search, context, environment, conversation_id) is already fully documented, including the 'omit to list across the whole hub' note. The description's environment preference and page=next_page hints add only marginal meaning over the schema. Baseline 3 applies when the schema does the heavy lifting.

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 (containers) plus the scope (in the Cycle hub, optionally scoped to one environment). An agent can distinguish this from list_environments, list_servers, and list_virtual_machines by the resource noun alone. No ambiguity about what the tool returns.

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?

Gives clear usage contexts: discover what exists, check current state, or disambiguate same-named containers. Also advises preferring the environment parameter to narrow results. However it never names an explicit alternative tool or a when-not-to-use condition, so it stops short of the top tier.

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