kaiten_get_sd_sla

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

No annotations are provided, so the description carries the burden of behavioral disclosure. 'Get' signals a read operation and no side effects, but the description gives no detail on return shape, error behavior, permissions, or whether the SLA policy is a plain read; it does not contradict 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?

A single, front-loaded sentence communicates the verb, object, and lookup key with no redundant words. It earns its place and leaves nothing to trim.

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 one-parameter getter with no annotations or output schema, the description plus the schema fully supplies the information an agent needs to invoke the tool correctly: a single UUID identifies the SLA policy. Absence of a return-value description is a minor gap given no output schema exists, but it does not block correct invocation.

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 description coverage is 100%; the sla_id parameter is already documented as 'SLA ID (UUID)'. The description's 'by ID' reinforces that the sole parameter is the identifier but adds no new syntax or format details, matching the baseline for complete schema coverage.

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 states a specific verb ('Get'), a specific resource ('Service Desk SLA policy'), and the lookup mechanism ('by ID'), which clearly distinguishes it from sibling list/create/update/delete SLA tools even without inspecting schemas.

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 the tool is for retrieving a single SLA when the ID is known, but it does not explicitly say when to prefer it over kaiten_list_sd_sla or kaiten_get_sd_sla_stats. This is clear context without exclusions or alternatives, so it falls at the implied-usage level.

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