hcm_list_checklists

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

The annotation readOnlyHint=true already signals a read operation, and the description's 'List' is consistent with that, so there is no contradiction. However, the description adds no behavioral detail beyond the annotation—it does not mention pagination, filtering, or the structure of the returned list, which would be valuable context for a tool with minimal annotations.

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 with no wasted words, which is efficient. However, it is under-specified to the point of being nearly tautological—it restates the tool's name without adding operational substance. True conciseness would preserve brevity while conveying necessary details.

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 that there is no output schema, no parameter descriptions, and only a one-line description, the tool is seriously incomplete. An agent would not know what to pass for q, how to handle pagination, what fields the response contains, or what distinguishes allocated checklists from others. The definition is inadequate for correct invocation.

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%, meaning none of the three parameters (q, limit, offset) are documented in the schema. The description does not explain any of them, leaving the agent to guess that q might be a query filter and limit/offset are pagination controls. This is a critical gap that the description fails to compensate for.

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 uses the specific verb 'List' with a clear resource 'allocated checklists,' which distinguishes it from sibling tools like hcm_get_checklist (singular retrieval) and hcm_allocate_checklist (creation). However, it does not clarify what 'allocated' means or define the scope, leaving some ambiguity.

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 such as hcm_get_checklist for retrieving a single checklist or hcm_allocate_checklist for creating one. The description offers no context for selection, so an agent has no basis to choose it over related tools.

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