get_list_cards

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action, omitting details such as whether the operation is read-only, pagination behavior, error handling for invalid list_id, or authentication requirements. The minimal description fails to inform the agent of behavioral traits.

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 concise sentence, which is efficient but under-informative. It front-loads the core purpose, but given the lack of annotations and parameter info, it could be slightly longer to include essential context without becoming verbose.

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 simple tool with one parameter, no output schema, and no annotations, the description is minimally complete but lacks key details like usage context and behavioral traits. It does not address potential pitfalls or provide enough information for the agent to use it confidently alongside sibling tools.

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 for the lack of parameter documentation. It does not explain the list_id parameter beyond its name, leaving its format, expected value type, or constraints undefined. The description adds no value to parameter understanding.

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 'Get all cards in a Trello list' clearly states the verb (get) and resource (cards in a list), distinguishing it from siblings like get_card (single card) and get_board_cards (cards in a board) by specifying 'in a Trello list'. However, it does not explicitly differentiate from get_board_cards, which also retrieves multiple cards but across 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?

No guidance is provided on when to use this tool over alternatives like get_board_cards or get_card. It does not mention context, prerequisites, or exclusions. The description lacks any usage direction.

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