Cm360.Placements.List

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose a meaningful trait — results are scoped to what the given CM360 user profile can see — but it omits read-only confirmation, pagination behavior, and rate/limit context that would matter for a list operation.

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 front-loaded sentence with no filler; the resource and the scoping constraint appear in the first pass. It is efficient, though the brevity leaves some behavioral detail on the table.

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?

An output schema exists, so return structure need not be described, and the tool has only one parameter. Still, with no annotations and zero schema description coverage, the description should say more about obtaining profile_id and about pagination for a list endpoint.

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%, so the schema only says profile_id is a string. The description partially compensates by tying the parameter to 'a CM360 user profile' whose visibility governs results, but it does not explain how to obtain a profile_id (the cm360.user_profiles.list sibling) or any format details.

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 ('placements'), reinforced by a parenthetical gloss ('ad-serving slots') and a scoping qualifier ('visible to a CM360 user profile'). This clearly separates it from the mutating sibling cm360.placement.update, though no sibling is named 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?

The phrase 'visible to a CM360 user profile' implies the tool requires a profile context and returns only that profile's placements, which is usable guidance. However, there is no explicit when-to-use/when-not statement and no reference to alternatives such as cm360.user_profiles.list for obtaining the profile_id.

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