trello_get_board_overview

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

Annotations already declare readOnlyHint: true, so the description does not need to repeat that. The description adds context about what data is included (lists, cards, deadlines, links) but does not disclose any additional behavioral traits such as performance, rate limits, or permission requirements. Since annotations cover the read-only nature, a 3 is appropriate.

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, clear sentence that front-loads the key information ('Panoramica completa'). Every word is useful and there is no redundancy 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 read-only tool with one parameter and no output schema, the description adequately explains the return content (lists, cards, deadlines, links). It could be slightly improved by mentioning whether the overview is paginated or if it returns all data in one call, but overall it is sufficient.

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% for the single parameter boardId, which already provides a description including the default value. The tool description does not add any meaning beyond that, 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 states 'Panoramica completa di una board: liste, card, scadenze e link' which clearly specifies a complete overview of a board including lists, cards, deadlines, and links. It distinguishes this tool from siblings like trello_list_boards, trello_list_lists, and trello_list_cards by providing a composite view.

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 explicit guidance on when to use this tool versus alternative tools like trello_list_boards or trello_get_board_activity. Usage is implied by the name 'overview', but the description lacks when/when-not statements or references to siblings.

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