create_board

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly states the mutation ('Create a new Trello board') and the return behavior ('Returns: The Trello API response containing the created board details'). It does not mention auth, error cases, or side effects, but for a one-parameter create operation this is sufficient.

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 appropriately sized, front-loaded with the core purpose, and then uses clear Args/Returns sections. Every sentence is necessary and there is no filler or redundancy.

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 only one simple required parameter, the description explains it, and an output schema exists for return details. The description is complete enough for an agent to invoke this tool correctly without additional context.

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 input schema contains no property descriptions (0% schema coverage), so the description's Args section adds real value by explaining that 'name' is 'the name to assign to the new board.' It fully clarifies the only parameter, though it does not add constraints like length or format.

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 opens with a specific verb and resource: 'Create a new Trello board.' This clearly distinguishes it from sibling tools like create_list, create_card, delete_board, and search. Even without additional context, an agent can tell exactly what operation this tool performs.

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?

The description implies the tool should be used when creating a Trello board, but it provides no explicit 'when to use' or 'when not to use' guidance. It does not name alternatives or conditions for choosing this tool over a sibling, leaving usage entirely implied.

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