cm_list_timezones

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

The description adds context beyond the annotations by specifying that the list contains 'valid timezone names accepted by the API'. The readOnlyHint annotation already indicates no side effects, but the description clarifies what the tool returns. No mention of pagination or ordering, but given zero parameters, the behavior is predictable.

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, front-loaded sentence. It conveys the tool's purpose directly without superfluous words. Every part of the sentence is essential.

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 has no parameters, no output schema, and a straightforward purpose, the description is complete. It sufficiently informs the agent about the tool's functionality and what to expect.

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 has no parameters, so the description does not need to provide parameter details. The baseline for 0 parameters is 4. The description does not add any parameter information, but none is needed.

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 tool retrieves a list of valid timezone names accepted by the API. It uses a specific verb ('Get') and identifies the resource ('list of valid timezone names'). This distinguishes it from sibling tools, which focus on other entities like campaigns, lists, or subscribers.

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 provides no explicit guidance on when to use this tool versus alternatives. However, the tool is simple with no parameters, so usage is intuitive. A higher score would require stating that this tool is for retrieving timezone names only, not for conversions or filtering.

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