get_card

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

With no annotations, the description carries behavioral disclosure. It does state what is included in the returned card (description, labels, due date, checklists, recent comments) and implicitly presents this as a read-only operation, but it doesn't mention permissions, error behavior, rate limits, or how 'recent' is determined.

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?

A single, front-loaded sentence with no filler; the colon-delimited list efficiently conveys the response scope. Every word earns 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?

For a one-parameter read operation, the description plus output schema is mostly sufficient. The main gaps are an explicit usage-rule statement and clarification of the 'recent' limit, but these are minor given the simple scope.

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 input schema only provides name/type/required for card_id and has 0% description coverage. The tool description never explains the card_id parameter, how to obtain it, or its accepted format; the agent must rely on the self-explanatory name.

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 uses a clear verb ('Get') and identifies the exact resource ('one card') while enumerating the payload ('description, labels, due date, checklists and recent comments'). This distinguishes it from sibling list_cards (which returns many) and get_board_info (a different resource).

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 intended use is implied: call this when you need the full detail of a single card. However, it never explicitly says when to prefer this over list_cards/search_trello or when not to use it, so the agent must infer the context.

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