Cm360.Floodlight Activities.List

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

With no annotations, the description carries the burden, and it does disclose one real behavioral trait: results are scoped to what a given CM360 user profile can see (a permissions/visibility constraint). However, it says nothing about pagination, result volume, or ordering, and read-only status is only implied by 'List'.

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?

One sentence, front-loaded with the verb and resource, with zero filler. Its brevity is close to under-specification rather than padding, but structurally it is clean.

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 values need not be described, but for a tool requiring a profile_id the description never explains how to obtain one, nor anything about pagination or result limits. Given zero annotation coverage, the definition leaves real gaps an agent must guess at.

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% for the single parameter, so the description must compensate. It does clarify that profile_id denotes the CM360 user profile whose visibility scope governs the listing, which adds meaning beyond the bare string type, but gives no format, source, or example value.

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 and resource ('List Floodlight activities') and adds a clarifying gloss ('conversion tags') plus the visibility scope ('visible to a CM360 user profile'). The resource is distinct enough from siblings like cm360.campaigns.list and cm360.placements.list that an agent can select it, 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?

There is no when-to-use guidance, no exclusions, and no mention of alternatives or prerequisites — notably, nothing says the profile_id should come from cm360.user_profiles.list. The usage is only inferable from the verb 'List'.

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