create_card

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

Without annotations, the description bears full responsibility for behavioral disclosure. It discloses that the tool creates a card, accepts optional settings, and returns the created card with id and name. It does not mention creation side effects or error conditions, but the core behavior 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?

The description is concise—two sentences—and front-loads the core action. It efficiently lists optional parameters without unnecessary elaboration, earning its place.

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 7 parameters, 0% schema coverage, and no annotations, the description covers the essential creation behavior and return values (which the output schema supplements). It omits the 'desc' parameter and error handling, but for a creation tool, the completeness is adequate.

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 coverage is 0%, so the description must compensate. It explains the meaning of parameters like list_id, name, pos (top/bottom), idLabels (comma-separated), due (ISO 8601), and dueComplete (true/false). However, it misses the 'desc' parameter, which is in the schema but not described.

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's purpose: 'Create a new card in a Trello list.' It specifies the action (create), the resource (card), and the container (list). It distinguishes itself from sibling tools like update_card or archive_card by focusing on creation.

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 explains when to use the tool (to create a card) and lists optional parameters like position and labels. However, it does not explicitly state when not to use it (e.g., if updating an existing card) or provide guidance on alternatives like create_board or create_list.

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