Create Board

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

Annotations already signal that this is a non-read-only, non-destructive operation. The description adds useful behavioral context by stating that the newly created board is returned with its ID and URL, which is especially valuable given there is no output schema to convey this.

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 compact and every sentence earns its place: it states the action, explains the conceptual role of boards, and notes the return value. No filler or redundancy is present.

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 two-parameter create operation, the description is largely complete: all parameters are documented in the schema, the return value is described due to the absent output schema, and annotations cover the safety profile. It does not discuss error cases or idempotency, but those are not essential for this straightforward creation tool.

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%, and both parameters are already well documented; account_slug even includes examples and guidance on where to obtain valid values. The tool description itself adds no additional parameter semantics, so the baseline score of 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 uses a specific verb and resource combination: 'Create a new board in a Fizzy account.' It also clarifies that boards are top-level containers for organizing cards, which distinguishes this tool from create_card and create_column without needing to read 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 description implies when to use the tool through the context that boards are top-level containers, but it never explicitly states when to choose this over alternatives or mentions any prerequisites beyond the account slug. Since no alternative create-board sibling exists, the lack of exclusions is somewhat mitigated, but the guidance is still only implied.

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