trello_project_overview

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

The description discloses that it returns boards, lists, and card titles. However, with no annotations, it should also mention that it is a read operation (implied but not stated), any size limits, or how 'project' is defined. Moderate transparency.

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?

Single, well-structured sentence that front-loads the key information. No unnecessary words or filler.

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 tool with one optional parameter and no output schema, the description is sufficiently complete. It covers the main components (boards, lists, card titles) and the dash board nature. Slightly lacks explicit read-only indication.

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 only parameter 'format' is fully described in the schema (enum json/markdown). The description adds no extra semantic value beyond what the schema provides. Baseline 3 for 100% 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 states it provides a 'dashboard view' of all boards for the project, including lists and card titles. It distinguishes from siblings like trello_get_board (single board) and trello_list_boards (list of boards only). However, it lacks an explicit verb like 'retrieve' or 'list', and 'dashboard view' is slightly vague.

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 is provided on when to use this tool versus the many sibling tools (e.g., trello_get_board for a specific board, trello_get_cards_in_list for a specific list). An explicit statement of scope and alternatives would be helpful.

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