List SLA Policies

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

Description adds critical behavioral info beyond annotations: the authentication requirement (admin vs agent) and that standard agents get 403. Annotations already indicate read-only/idempotent, so no contradictions.

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?

Three concise sentences with front-loaded purpose. Every sentence adds value: purpose, use case, and permissions. No redundant or missing 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?

Covers purpose, use case, and permissions. Could benefit from explicitly stating it returns an array of policy objects, but the description's high-level overview is sufficient for selection.

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% with well-described pagination params. Description adds no extra parameter-level detail beyond the schema, so 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?

Description clearly states the tool lists SLA policies with filter conditions and per-priority targets. It distinguishes from siblings like get_ticket (per-ticket SLA) by specifying it retrieves the policy configuration itself.

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?

Explicitly states when to use (reconstruct deadlines deterministically) and when not to (use get_ticket/search_tickets for per-ticket SLA). Also specifies required permissions (admin token) and notes alternatives for standard agents.

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