Cm360.Reports.List

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

With no annotations, the description carries the full burden; it does disclose the meaningful behavioral trait that results are filtered by profile visibility/authorization. However, it says nothing about pagination, result limits, or whether inactive/shared reports are included.

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 tight sentence, front-loaded with the verb-resource pair. It is efficient, though some of that efficiency comes at the cost of missing detail rather than genuine 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 exists, so return values need not be explained, and the profile-scoped visibility is stated. Still missing are the meaning of the required profile_id and basic guidance on when this list is the right entry point versus running or creating reports.

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 single parameter profile_id is never mentioned or explained. The phrase "visible to a CM360 user profile" only obliquely hints that profile_id refers to a CM360 user profile identifier, leaving the agent to infer format and provenance.

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 report definitions") plus a scope qualifier ("visible to a CM360 user profile"), which cleanly separates it from cm360.report.run and cm360.report.insert. It does not explicitly name those siblings, so it stops short of full differentiation.

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 indication of when to call this versus cm360.report.run (which likely executes a saved report) or cm360.report.insert. There is no mention of prerequisites such as obtaining a profile_id first via cm360.user_profiles.list.

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