get_placement_decisions

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

With no annotations, the description carries the behavioral disclosure burden. It communicates a read-only list operation and the key output behavior ('showing selected clusters'), but it does not disclose behavior around the optional cluster filter, empty results, or failure cases. Core behavior is transparent, but depth is limited.

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 sentence that front-loads the verb, resource, and scope. There is no redundant wording, and every phrase adds meaning.

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 output schema covers return-value structure, so that is not a gap. However, the description leaves the optional cluster parameter's role ambiguous and does not mention namespace as a lookup context, which an agent needs to call the tool correctly with confidence.

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%, and the schema properties only provide titles. The description maps placement_name via 'for a Placement' and hints at cluster via 'selected clusters', but it never explains the namespace parameter or whether the cluster parameter filters input or describes output. It only partially compensates for the bare schema.

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?

Uses a specific verb ('List') and a specific resource ('PlacementDecisions') with clear scope ('for a Placement') and output focus ('showing selected clusters'). This clearly distinguishes it from sibling list_placements, which lists the placements themselves.

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 implies the use case: call this when you need a placement's selected clusters. However, it does not explicitly state when to prefer this over list_placements or other placement-related tools, nor does it give any exclusions or alternative routing.

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