list_board_items

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

No annotations exist, so the description carries the full burden. It mentions 'cursor pagination' as a behavioral trait. However, it does not disclose idempotency, auth requirements, or rate limits. The behavior is implied as read-only (listing), but not explicitly stated.

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 sentences, front-loaded with purpose and a key guideline. While concise, it lacks structure for parameter details. Every sentence earns its place, but could be expanded slightly for completeness.

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?

With four parameters and no schema descriptions, the description is incomplete. It provides a prerequisite but fails to document pagination mechanics or the optional includeColumnValues. Even with an output schema present, the param coverage is insufficient for correct invocation.

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 description coverage is 0%, so the description must compensate. It hints at cursor and limit via 'cursor pagination', but does not explain parameters like boardId, limit, cursor, or includeColumnValues. Users cannot understand how to use these parameters from the description.

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 lists items from a board using cursor pagination. The verb 'list' and resource 'items from a board' are specific, and the mention of cursor pagination distinguishes it from siblings like 'list_boards' and 'get_item'.

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 a prerequisite ('Call get_board_details first'), which guides usage. However, it does not specify when to use this tool vs alternatives like 'get_item' or 'list_item_updates', nor does it mention when not to use it.

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