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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds a behavioral detail about what the lane shows (which task sits in which board column), which is useful, but does not disclose additional traits like error handling or return format, so it stays at a mid score.

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 sentence, immediately front-loaded with the verb and resource, and contains no filler. Every clause adds information about the operation's purpose and output.

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 the tool's simplicity (one parameter, no output schema) and strong sibling context (e.g., list_sprint_lanes, move_sprint_lanes), the description adequately explains the tool's function and result. It could mention error behavior (e.g., not found), but that is not essential for a basic retrieve.

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 schema contains only a generic 'pk' description ('The primary key of the resource') with 0% schema coverage. The description's 'by id' clarifies that pk is the lane's identifier, adding meaning beyond the schema. With only one parameter and this clarification, it earns a 4.

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 'Retrieve a single sprint board lane by id' with a specific verb and resource, and adds 'showing which task sits in which board column for its sprint' which clarifies the tool's unique output. This clearly distinguishes it from list_sprint_lanes (plural) and other sprint-related tools.

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 usage for fetching a single lane by ID, with the word 'single' contrasting with list-style tools. It provides clear context but does not explicitly mention alternatives or exclusions, so it stops short of a 5.

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