Get Trello Board

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

With no annotations, the description's minimal statement 'Return metadata' does not disclose behavioral traits such as whether it is read-only, what 'metadata' includes (e.g., lists, cards?), or any potential side effects. The agent must infer safety from the name alone.

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 that front-loads the purpose. No extraneous information, but could benefit from slight elaboration (e.g., what metadata contains) without becoming verbose.

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?

The tool has no output schema, and the description omits what 'metadata' includes (e.g., board name, description, lists?). Given the simplicity and sibling tools, this under-specifies the return value. Also lacks differentiation from similar tools.

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 coverage is 100% with one parameter boardId described as 'Board id. Defaults to TRELLO_BOARD_ID.' The description adds no extra meaning beyond the schema, so baseline score of 3 applies.

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 'Return metadata for a Trello board', specifying the verb 'return' and resource 'metadata for a Trello board'. This distinguishes it from siblings like trello_get_card (which returns card metadata) and trello_list_boards (which lists all board summaries).

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 alternatives (e.g., trello_list_boards for summaries, trello_get_card for cards). The description does not include any contextual hints about appropriate scenarios.

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