cmw_list_limits

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

With no annotations available, the description carries the full burden. 'List all defined limits' clearly indicates a read-only operation, but it does not disclose edge cases (e.g., empty list), return format, or any prerequisites. For a simple zero-parameter tool, this is minimal but adequate.

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 concise sentence with no superfluous words. It communicates the operation effectively and efficiently.

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 (no params, no output schema), the description is nearly complete. The meaning of 'limits' is clarified by the sibling tools (e.g., define_limit, check_limits), and the operation is fully captured. However, it could slightly benefit from mentioning that it returns a list, but that is already implicit in 'list'.

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 tool has zero parameters, so the baseline is 4. There is no parameter information needed, and the description does not need to compensate for schema gaps. The schema is trivially empty and fully covered.

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 'List all defined limits' uses a specific verb (list) and resource (defined limits), clearly distinguishing it from sibling tools like define_limit, check_limits, and clear_limits. This is a focused and unambiguous purpose.

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 guidance on when to use this tool versus alternatives. It does not mention that it is a read-only retrieval or that it should be used before checking or clearing limits. The usage is implicitly obvious from the name, but no explicit context or exclusions are given.

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