board_create

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

No annotations are provided, so the description carries the full burden. It does disclose meaningful behavior: boards default to private, workspaceId places the board in an org, and visibility is restricted to enumerated values. It says nothing about permission requirements, whether the creator becomes an admin, or rate limits for a mutation tool.

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?

A single front-loaded sentence that opens with the usage trigger and then layers the behavioral constraints. It is slightly run-on with three comma-joined clauses, but there is no filler or repetition.

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?

With no annotations and no output schema, the description should carry more of the operational burden. It covers visibility and workspace placement adequately but leaves auth requirements, what the created board response contains, and failure modes unaddressed for a 4-parameter mutation.

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%, so the baseline is 3. The description reinforces the private default and the workspaceId placement, but that information is already present in the schema's own parameter descriptions; it adds no new syntax, format, or edge-case detail beyond it.

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?

States a specific verb and resource ('creating a new Trello board') and immediately scopes it by describing the default visibility and workspace placement. An agent can distinguish it from the read-oriented board siblings (board_get, list_boards, workspace_boards) without inspecting the schema.

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 'Use when creating a new Trello board' trigger is explicit, and the clause about only supporting explicit private/workspace/public visibility sets a constraint on invocation. However, it names no alternative path (e.g., creating a board from a template or moving an existing board) and gives no prerequisites such as required auth scope.

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