accelo_count_staff

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

No annotations are provided, so the description carries the full burden. It doesn't disclose what 'filters' supports, whether the count is exact or approximate, whether it requires specific permissions, or what the response contains beyond a number (no output schema). Minimal transparency for a query tool.

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 that is efficient and contains no redundant or filler content. Appropriate length given the limited information provided.

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 filterable count tool with one entirely undocumented parameter, no annotations, and no output schema, the description leaves large gaps. It doesn't define filter syntax, result semantics, or usage context relative to sibling list tools, so an agent cannot fully rely on it without external knowledge.

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% – the single 'filters' parameter is an untyped arbitrary object with no documented properties. The description merely restates 'matching the given filters' without adding syntax, allowed fields, or format details, leaving the parameter essentially opaque.

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 (count) and resource (staff members), which is clear enough. However, the phrase 'matching the given filters' adds no scope beyond what the name implies, and there are no siblings with overlapping intent among accelo_list_staff or accelo_get_staff to require differentiation.

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 on when to use this count tool versus accelo_list_staff or accelo_get_staff. With no exclusions or alternatives mentioned, the agent must infer usage from the name alone.

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