list_board_lanes

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

Annotations already declare readOnlyHint=true. The description adds the explicit statement that it does not move cards, which reinforces but does not significantly expand behavioral disclosure. No additional traits like auth needs or rate limits are mentioned.

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: the first describes the core function, the second provides usage and behavioral context. Every word adds value with no redundancy.

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 lacking an output schema, the description adequately describes return content (lanes with card summaries and pagination metadata). The tool has only 2 parameters with clear schema descriptions, and the description adds usage flow context, making it complete for agent understanding.

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?

Input schema has 100% coverage, so baseline is 3. The description adds context by mentioning pageSize limits cards per lane and implying boardId comes from list_boards, providing usage guidance beyond the schema.

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 the tool resolves a board's query widgets into lanes with card summaries and pagination metadata, using specific verbs and resource. It distinguishes from sibling tools by noting it is used after list_boards identifies a board.

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 provides explicit usage context ('Use after list_boards identifies a board') and behavior restrictions ('This is read-only and does not move cards'). It lacks explicit when-not-to-use or alternative tools, but the context is sufficient for agent decision.

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