Cm360.Campaigns.List

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

No annotations are provided, so the description carries the full burden. It does disclose a real behavioral trait — results are permission-scoped to what the profile can see — but says nothing about read-only semantics, pagination, result caps, or rate limits, which matter for a list endpoint.

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. It is efficient, though its brevity edges into under-specification rather than optimal density.

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 covers return values, but with zero annotation coverage and an undocumented required parameter, the description leaves the agent without the two things it needs: how to get profile_id and how results are paged/limited.

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 0% and there is one required parameter. The description mentions "user profile" but never names profile_id, explains its format, or points to cm360.user_profiles.list as the way to obtain it — the exact gap the schema leaves.

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?

Specific verb+resource ("List campaigns") plus a scoping qualifier ("visible to a CM360 user profile") that distinguishes it from generic campaign listings. The cm360 namespace separates it from dv360.campaigns.list, but the description itself never acknowledges that sibling.

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 when-to-use, when-not-to-use, or alternative is stated. The agent must infer that this is the enumeration step in a CM360 workflow and must already know that cm360.user_profiles.list supplies the required profile_id.

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