basecamp_list_cards

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

With no annotations, the description carries the full burden. It transparently discloses the auto-paginating behavior, the aggregation into a single array, and the effect of single_page. It does not mention output fields or error conditions, but the key non-obvious behavior (pagination) is well covered.

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 the main purpose, and every phrase adds value. It explains the default behavior, the edge case (224-card column), and the alternative mode without fluff.

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?

For a list tool with four params and no output schema, the description covers the essential behavioral aspects and parameter usage. It lacks an explicit note about return format, but the aggregation behavior is described. Given the tool's simplicity, it is sufficiently complete.

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 50% (page and single_page have descriptions, project_id and column_id do not). The description adds meaningful semantics beyond the schema by explaining default values and the intent of single_page for UI-style pagination. Though it doesn't clarify the ID parameters, these are self-evident.

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 opens with a clear verb+resource: 'List cards in a column.' It is specific and distinguishes itself from sibling tools like basecamp_list_card_ids (which lists only IDs) and basecamp_get_card (which gets one card). The scope is unambiguous.

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 includes guidance on when to use the default auto-paginating behavior versus passing single_page for UI pagination. It does not explicitly mention alternatives like list_card_ids or when not to use this tool, but the pagination explanation provides clear context for usage.

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