cloud_list_placement_groups

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

With no annotations, the description carries full burden but only says 'List', omitting details like read-only nature, pagination behavior, default page size, or rate limits. As a list operation, it likely returns all groups by default, but this is not disclosed.

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 very concise (3 words), but extreme brevity reduces informativeness. It earns its place as a clear statement of purpose, but lacks structure or elaboration that would aid the agent.

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?

Given the tool has 5 parameters, no annotations, and an output schema (not detailed), the description is incomplete. It does not mention pagination, filtering capabilities, or how parameters relate to the list operation. The presence of sibling tools like cloud_get_placement_group implies use cases, but these are not addressed.

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%, yet the description adds no explanation for any of the 5 parameters (page, per_page, name, type, label_selector). While parameter names are somewhat self-explanatory, the description fails to add meaning beyond what the schema provides, leaving the agent without clarity on usage.

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 'List placement groups' states the action (list) and resource (placement groups) clearly. It distinguishes from siblings like cloud_create_placement_group and cloud_delete_placement_group, making the tool's purpose unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives like cloud_get_placement_group for a single group. The description lacks any when-to-use or when-not-to-use context, forcing the agent to infer from the name alone.

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