swsd_create_incident_task

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

Adds 'WRITE — does not retry on transient failure' beyond annotations (readOnlyHint false, idempotentHint false). This provides useful error-handling context. Still lacks details on auth or side effects for openWorldHint true.

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?

Two clear sentences plus a tagline. No filler, front-loaded with action. Efficient and well-structured.

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, parameters, and return value. Missing discussion of side effects (openWorldHint true) or idempotency implications. Adequate for a creation tool with good annotations.

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 covers 100% of parameters with descriptions. Description repeats required/optional info and adds that the created task is returned, which is not in the schema. Baseline 3, plus slight value from return info.

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?

Starts with 'Create a new sub-task on a SWSD incident', clearly stating verb and resource. Distinguishes from sibling tools like swsd_list_incident_tasks or swsd_update_task_state.

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?

Lists required and optional parameters, aiding usage, but does not explicitly state when to use this tool versus alternatives (e.g., swsd_create_incident). No 'when not to use' guidance.

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