list_cards_in_column

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

Without annotations, the description partially covers behavior by mentioning pagination support, which is key for a listing tool. However, it does not disclose details like ordering, error handling for invalid column IDs, or whether the response is complete or incremental. The added context that 'cards are email threads or tasks' helps but is insufficient for full transparency.

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 with three sentences that front-load the purpose and pagination details. Every sentence adds value without redundancy, achieving high efficiency.

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 4 parameters, no output schema, and no annotations, the description is moderately complete. It explains pagination and the nature of cards, but does not describe return format (e.g., fields returned) or pagination metadata (e.g., total count). For a list tool this leaves gaps in agent understanding of the response structure.

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 already provides 100% coverage with clear descriptions for page, limit, boardId, and columnId. The description adds no additional parameter semantics beyond stating pagination, which is already implied by the 'page' and 'limit' parameters. Baseline score 3 is appropriate.

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 explicitly states the verb 'List', the resource 'cards in a specific column', and the scope 'of a DragApp board', which clearly defines the tool's purpose and distinguishes it from siblings like 'list_boards' or 'list_columns'.

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 no guidance on when to use this tool versus alternatives, such as 'get_card' for a single card or 'filter_threads' for card-like threads. It lacks explicit when-to-use/when-not-to-use instructions, leaving the agent to infer context from the tool name.

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