kaiten_attach_card_sla

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action and does not mention whether attaching replaces an existing SLA, requires specific permissions, is idempotent, or has any side effects on SLA measurements.

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?

The description is a single, front-loaded sentence with no filler or redundant content. It conveys the core operation in the fewest words possible.

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 two-parameter mutation, the description provides a minimal viable invocation path. However, with no annotations, no output schema, and no usage/behavior guidance, it leaves gaps about the operation's effects and prerequisites that an agent may need to know.

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%, with card_id and sla_id already described in the input schema. The tool description does not add further semantic meaning beyond the schema, but it also does not need to because the schema is sufficient.

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 'Attach an SLA policy to a card' clearly identifies the verb (attach), the resource (SLA policy), and the target (card). It is distinguishable from sibling tools like kaiten_detach_card_sla and kaiten_get_card_sla_measurements without requiring schema inspection.

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 gives no guidance on when to use this tool versus alternatives such as kaiten_detach_card_sla or kaiten_create_sla_rule. There are no conditions, exclusions, or contextual signals that would help an agent decide between related SLA operations.

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