Search Trello

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

No annotations and the description only says 'Search cards, boards, and organizations.' It fails to disclose whether the tool is read-only, what it returns, or any side effects. This is insufficient for a non-annotated tool.

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 sentence, concise and front-loaded. However, it could be restructured to list searchable model types or highlight the optional modelTypes parameter.

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 no output schema, the description lacks return value details, pagination, or result format. For a search tool, this is a significant gap, making it hard for the agent to interpret results.

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 100% with clear parameter descriptions (e.g., 'Search query', 'Comma-separated model types'). The tool description adds no extra parameter meaning, so baseline 3 is appropriate.

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 searches for cards, boards, and organizations, with a specific verb and resources. It distinguishes from sibling tools which are focused on individual CRUD operations, but could explicitly mention the broad search scope.

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 on when to use this tool versus alternatives like get_card or search_members. The agent is not informed of prerequisites or when not to use it, relying on implicit understanding.

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