sla_breach_report

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

No annotations provided, and description only hints at read-only nature ('Find'). Fails to disclose behavior around the hours_ahead parameter or any side effects, leaving agent uncertain about tool impact.

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?

Single sentence but too terse; omits essential details like parameter meaning and usage context. Conciseness sacrifices necessary information.

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?

Despite having output schema, the description lacks parameter explanation, no usage guidance, and no behavioral context. Agent likely cannot invoke tool correctly without additional 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?

The single parameter 'hours_ahead' has no description in schema or tool description. Agent cannot determine its meaning or usage, despite it being the key parameter for controlling report scope.

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 clearly states verb 'Find' and resource 'tickets', specifying scope as 'breaching or approaching SLA targets'. This distinctly identifies the tool's purpose among sibling report 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 guidance on when to use this tool versus alternatives like stale_ticket_report or response_time_analysis. Agent must infer usage from tool name and context.

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