update_swimlane

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

No annotations provided, so the description is the main source. It discloses partial update behavior, validation error condition, and success response format. Missing details on side effects or idempotency, but fairly transparent for an update action.

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 concise sentences with no filler. Front-loaded with the action and followed by critical usage notes. Every sentence adds value.

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?

Despite clear usage guidance, the description is incomplete due to missing parameter details in both schema and description. The tool cannot be used correctly without specifying which fields are updatable. No output schema, but the return format is described.

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 description mentions swimlane_id and additional fields, but the input schema has no properties. This creates a mismatch; the description does not specify which fields are valid, leaving ambiguity. The schema coverage is 100% only because there are no params to cover.

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 clearly states it updates a swimlane (verb+resource) and mentions partial update. It distinguishes from reordering by referencing move_swimlane, but the lack of parameters in the schema undermines clarity.

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 NOT to use: 'NOT for reordering — use move_swimlane instead.' Also specifies required fields condition: 'At least one field besides swimlane_id must be provided — otherwise VALIDATION_ERROR.'

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