Get Card

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 'Get detailed information,' which conveys a read operation, but does not mention response structure, what fields are included, error handling, or that includeMarkdown alters the response type. No side effects or authorization needs are disclosed.

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 with no redundant words. It is front-loaded with the verb and resource, making the purpose immediately clear.

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 get tool with two parameters and full schema coverage, the description is adequate but leaves gaps: there is no output schema, so the agent cannot know the return format or fields, and the description does not mention the markdown option. However, the tool's simplicity mitigates these issues.

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?

Both parameters (cardId and includeMarkdown) are fully described in the input schema, so the schema already covers their meaning. The description adds no additional parameter context, but baseline 3 is appropriate due to 100% schema coverage.

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 specifies the action ('Get') and the resource ('detailed information about a specific Trello card'). This distinguishes it from sibling tools like get_my_cards or get_cards_by_list_id, which target different scopes.

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 implies usage for a single card by saying 'a specific Trello card,' but provides no explicit guidance on when to use it instead of alternatives. No alternative tools or exclusions are mentioned, leaving the agent to infer from context.

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