list_active_slas

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and openWorldHint=true, indicating safe, idempotent behavior. The description adds that filters are optional, which is minor context. No additional behavioral traits are disclosed beyond this.

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?

A single sentence containing all essential information: action, resource, and optionality of filters. No extraneous words; every part earns its place.

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?

The tool is a straightforward list operation with clear parameters and annotations. It does not explain return values, but this is typical for list tools and not critical. Complete enough for its complexity.

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 describes both parameters (query and limit) with full coverage (100%). The description only rephrases 'optional filters', adding no new semantic information. Baseline 3 is appropriate as the schema handles parameter meaning.

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 'List active SLA records with optional filters' clearly states the verb 'list', the resource 'active SLA records', and the scope 'with optional filters'. It distinguishes itself from sibling tools like 'get_sla_details' which retrieves a single SLA.

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 for listing active SLAs, and the name aligns with this purpose. It does not explicitly mention when not to use it or suggest alternatives, but the context is clear enough for a simple list operation.

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