accelo_count_checklists

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

No annotations are provided, so the description carries the full behavioral burden. "Count" implies a read-only operation, but the description does not state side-effect freedom, required permissions, rate limits, or any other behavioral traits.

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?

A single front-loaded sentence with no wasted words. However, its extreme terseness leaves key semantics unaddressed, so it is concise but not maximally useful.

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 count tool, the description is minimally stated, but the filters parameter is completely undocumented and there are no annotations. It should at least clarify whether filters are optional or how they are structured.

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 only parameter, filters, is named but not explained; schema description coverage is 0%. The description does not add filter syntax, structure, or examples, so it fails to compensate for the schema gap.

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?

States a specific verb and resource: "Count checklists" with filter scope. It distinguishes counting from listing implicitly, though it does not explicitly name the sibling accelo_list_checklists alternative.

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 phrase "matching the given filters" implies the tool is for filtered counting, but it gives no explicit when-to-use guidance. It does not mention when to use this instead of accelo_list_checklists or other count siblings, nor any exclusions.

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