manage_lane

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

Beyond the destructiveHint annotation, the description warns that delete removes the lane and unassigns all bars. It also states failure conditions (create without name, update/delete without lane_id). This adds substantial behavioral context.

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 concise: four sentences covering purpose, usage examples, action-parameter mapping, and warnings. It is front-loaded and every sentence adds value without unnecessary detail.

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?

Given no output schema, the description states what is returned (object on create/update, confirmation on delete). It also covers failure modes and prerequisite information (get IDs from get_roadmap_lanes). This provides sufficient context for a CRUD tool.

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 coverage is 100%, so baseline is 3. The description adds meaning by linking parameters to actions (create uses name, update/delete use lane_id) and specifying required conditions. This aids correct parameter selection beyond the schema alone.

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?

Clearly states the tool's purpose: 'Create, update, or delete a lane on a roadmap.' The verb-resource combination is specific, and the examples ('Add Backend lane', 'Rename Mobile lane', 'Delete lane') distinguish it from sibling tools like manage_bar or manage_milestone.

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?

Provides concrete usage scenarios with 'USE WHEN' examples and action patterns. It also notes prerequisites (get ID from get_roadmap_lanes). However, it does not explicitly state when not to use the tool or suggest alternatives, which would improve guidance.

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