list_csm_accounts

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

The description aligns with annotations (readOnlyHint=true) and adds no contradictory information. However, it does not elaborate on potential behavioral nuances like result ordering, pagination behavior beyond the limit parameter, or that it filters by active accounts by default. Annotations already declare safety, so a minimal description is acceptable but not exceptional.

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?

The description is a single sentence that is appropriately front-loaded with the action and resource. Every word adds value; there is no wasted text. It is concise and effective for a simple list tool.

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?

Given the tool's simplicity (3 optional parameters, no output schema, readOnlyHint), the description is minimally adequate. It does not describe the return format or any constraints beyond what the schema provides, but for a list operation with good annotations, this is sufficient but not thorough.

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?

The input schema covers all parameters with clear descriptions (limit, query, active). The description only mentions 'optional search filter' which is covered by the schema. With 100% schema description coverage, the baseline is 3; the description adds no additional meaning beyond the 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?

The description clearly states the action ('List') and the resource ('customer accounts'), and mentions the optional search filter, which distinguishes it from sibling tools like get_csm_account (singular) and other list tools for different entities.

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 guidance is provided on when to use this tool versus alternatives (e.g., search_csm_accounts or more specific list tools). It does not mention that it defaults to active accounts or that the query filter is name-based.

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