get_alert_violations

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

No annotations provided. Description fails to disclose behavioral traits such as read-only nature, pagination, or what 'recent' means (hours parameter not mentioned). Agent cannot infer safety or side effects.

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?

One-sentence description is concise but omits critical details like return format. Could be improved by front-loading key behavioral info while maintaining brevity.

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 simple read tool with one parameter and no output schema, the description should at least mention what is returned (e.g., list of violations/incidents) and clarify the time window. Current text is too vague for effective agent use.

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?

Single parameter 'hours' is fully described in the schema (100% coverage). Tool description adds no extra meaning beyond 'Number of hours to look back (default: 24).' Baseline score of 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?

Description uses verb+resource 'Get recent alert violations and incidents', clearly stating the tool retrieves both violations and incidents. It distinguishes from sibling get_incidents by covering both types, though ambiguity remains about whether it returns combined or separate lists.

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 tool vs siblings like get_incidents or other retrieval tools. Lacks context for prerequisites, recommended use cases, or when not to use it.

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