qobrix_count

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

With no annotations, the description carries the safety/behavior burden. It discloses that the tool returns only a count and no data payload, and that it's faster/lighter, which is the key behavioral trait. It does not mention error cases or auth requirements, but for a count operation these are less critical.

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 front-loaded with the core purpose, quickly states the performance benefit, then provides three compact examples. Each sentence serves a distinct function; no redundant or filler content.

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?

The description explains the return type (total count, no payload) and gives representative examples for the search DSL. It could mention output format or edge cases, but the examples and performance note cover the main usage scenarios adequately.

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 coverage is 100%, so baseline is 3. The description adds value with three concrete example search expressions spanning different resources and operators, illustrating how to combine filters and use shortcuts like THIS_MONTH. This exceeds the schema's already detailed parameter documentation.

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 opens with a specific verb and resource: 'Count records matching a search expression', explicitly distinguishing from list/fetch tools by stating it returns only the total count, no data payload. This clearly separates qobrix_count from sibling search/list tools.

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?

It explicitly says 'Faster and lighter than fetching records when you only need a number', giving clear when-to-use context. It doesn't name specific alternative tools or exclusions, but the general fetch vs count distinction is clear.

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