cm_list_people

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

Annotations confirm readOnlyHint=true, and the description adds 'active or invited' to clarify scope. However, it does not disclose potential limits, pagination, or whether the list includes all fields or summary data.

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, clear sentence with zero fluff. It is appropriately front-loaded and efficient.

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?

For a simple list tool with one parameter and no output schema, the description is mostly adequate. However, it could mention what fields are returned (e.g., names, emails) or note that only active/invited people are included, which is already stated.

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?

Only one parameter (clientId) exists, and its schema description fully covers its meaning. The tool description adds 'for a client' which is redundant with the parameter name. No additional semantic value 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 'List all (active or invited) people for a client,' using a specific verb and resource. It distinguishes from siblings like cm_get_person (single person) and cm_add_person (create) by focusing on listing multiple people.

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 description implies the tool should be used to obtain a list of people, but it does not explicitly state when to use it over alternatives like cm_get_person or cm_get_client_suppression_list. No exclusions or context triggers are provided.

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