get_board_details

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

Discloses that includeDetails=true produces large responses and provides parameters to control detail (compact, descriptionMaxLength). No annotations provided, so description carries full burden. Could mention authentication or return format more, but covers key behavioral aspects.

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?

Two sentences covering purpose and usage guidelines. Front-loaded with primary action, then gives clear recommendations. No redundant information.

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?

Adequate for a tool with 6 parameters and no output schema. Explains key parameter (includeDetails) well and references sibling tools. Could describe return structure or error conditions, but sufficient for typical use.

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%, but description adds context: emphasizes default behavior, warns about large responses, and explains how parameters like compact affect output. Adds meaning beyond schema.

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?

Clear verb ('Get information') and resource ('a Trello board'). Distinguishes from siblings by recommending get_card and trello_get_list_cards for specific card data, and mentions board metadata and lists specifically.

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?

Explicitly recommends starting with includeDetails=false and using other tools for drill-down. Warns about large responses with includeDetails=true and suggests only using for small boards needing a full overview.

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