saas_alerts_events_count_advanced

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds value by stating it executes a raw Elasticsearch query body and does not fetch full records, which clarifies the efficiency and return type. However, it does not describe the exact response format or any potential query limitations.

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, front-loaded sentence that effectively conveys the core purpose and a key differentiator. There is 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?

For a one-parameter tool with strong read-only/idempotent annotations, the description is reasonably complete. It covers the main purpose and the fact that it does not return records. However, it lacks explicit guidance on when to prefer this over other count/query tools and does not state the return value structure, though 'count' implies a numeric result.

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 input schema already provides a description for the 'query' parameter ('Elasticsearch query body'). The description repeats this as 'raw Elasticsearch query body' without adding additional semantics, constraints, or examples. With 100% schema coverage, the description does not significantly enhance parameter understanding.

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 clearly states the verb and resource: 'Count events using a raw Elasticsearch query body'. It also distinguishes itself from sibling tools by adding 'without fetching full records', clarifying that this tool returns only a count rather than full records, setting it apart from query 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?

No explicit guidance is given on when to use this tool versus the simpler saas_alerts_events_count or saas_alerts_events_query_advanced. The description implies it is for raw-query counting, but fails to mention alternatives, exclusions, or context for use.

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