accelo_count_activity_threads

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. It does not disclose that this is a read-only operation, what permission or rate limits apply, how filters are interpreted, or whether the count is exact or approximate.

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 definition is a single, front-loaded sentence with no wasted words. It is appropriately concise, though its brevity contributes to the overall lack of detail.

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 count tool with no annotations, no output schema, and 0% schema description coverage, the description is insufficient. It omits filter structure, return behavior, and routing among sibling count/list tools.

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%, and the single filters parameter is a generic object with no documented properties. The description merely says 'given filters' without adding any key names, value formats, or syntax beyond what the schema already lacks.

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 states a specific verb (Count) and resource (activity threads), making the tool's basic function clear. It does not explicitly differentiate itself from sibling tools like accelo_list_activity_threads or accelo_count_activities, but the count-versus-list distinction is inferable.

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?

There is no guidance on when to use this tool versus accelo_list_activity_threads or other counting siblings. The phrase 'matching the given filters' implies filtering but does not explain when counting is preferred over listing.

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