list_cards

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

No annotations provided, so description carries full burden. It details behavior for different pathspec levels (run, step, task) but lacks information on side effects, permissions, rate limits, or what happens when no cards exist.

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?

Well-structured with a concise main sentence, followed by a bulleted explanation of pathspec levels and a clean Args list. Every sentence adds value; no 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?

Covers input parameters and usage behavior. Since an output schema exists, the description does not need to explain return values. Slightly missing explicit mention of output format, but output schema fills that gap.

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 coverage is 0%, so description must compensate. It provides brief parameter descriptions (e.g., 'Only list cards of this type') but adds only basic meaning beyond the schema titles. Does not elaborate on format or constraints.

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?

Clearly states 'List cards attached to a run, step, or task' and differentiates from sibling 'get_card' by explaining this discovers cards before retrieval. The verb and resource are specific and the scope is well-defined.

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?

Explicitly says 'Use this to discover available cards before retrieving them with get_card,' providing clear usage context. However, no explicit when-not-to-use or alternative tools beyond get_card are mentioned.

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