saas_alerts_events_query_advanced

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds no additional behavioral context such as potential performance impacts, result size limits, or error handling for arbitrary query bodies. It is not contradictory but adds minimal value beyond the annotations.

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?

Two concise sentences, front-loaded with the primary action and resource. Every word adds value—'advanced', 'raw', 'maximum flexibility' all contribute to understanding. No redundancy or extraneous 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?

Given the tool's complexity (raw ES query) and absence of an output schema, the description is minimal and does not explain the return format, pagination, or potential risks (e.g., large result sets). Annotations mitigate safety concerns but the behavioral context remains incomplete for an advanced query tool.

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 covers 100% of parameters and already includes an example query body. The description adds 'raw Elasticsearch query body' and 'maximum flexibility', which reinforces the schema but does not provide deeper semantic explanation beyond what the schema offers. With full schema coverage, baseline 3 is appropriate.

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 uses a specific verb ('Execute') and names the exact resource ('SaaS Alerts events index'), clearly distinguishing this from siblings like saas_alerts_events_query by emphasizing 'advanced' and 'raw Elasticsearch query body'. It conveys the tool's unique purpose of providing maximum flexibility through raw queries.

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 description implies usage context: it's for advanced queries needing raw ES bodies, which is clear guidance on when to choose this tool. However, it does not explicitly mention simpler alternatives (like saas_alerts_events_query) or state when NOT to use it, so it falls short of full exclusion guidance.

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