cloud_list_placement_groups

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

No annotations are present, so the description must fully disclose behavior. It states the tool is read-only and free, and that it returns a compact view by default. However, it does not disclose any other behaviors such as pagination, rate limits, or required permissions. The description is sparse.

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 description is extremely concise: three short phrases in a single line. All information is front-loaded and no unnecessary words. Every sentence earns its place.

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?

The tool has 3 parameters with nested objects and no output schema. The description does not explain what a placement group is, nor what the compact vs verbose output contains. The agent lacks enough context to fully understand the return value or the meaning of parameters beyond their names. Significant gaps remain.

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% with parameter descriptions, so baseline is 3. The description adds value by stating 'Compact by default,' which directly relates to the 'verbose' parameter, clarifying a behavioral aspect beyond the schema. This elevates the score to 4.

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 clearly states 'List placement groups', specifying the verb and resource. It also adds 'Read only, free, Compact by default' which provides scope. However, it does not explicitly differentiate from sibling list tools beyond the resource name, which is adequate but not exceptional.

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 description mentions 'Read only, free' implying it is safe and costless, but does not provide explicit guidance on when to use versus alternatives, no exclusions or prerequisites. The agent must infer usage context from the name and read-only hint.

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