create_board

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

The description claims idempotency ('Idempotent by exact active board name'), but the annotations set idempotentHint to false. This is a direct contradiction, significantly undermining transparency. No other behavioral details (e.g., side effects, permissions) are mentioned.

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 only two sentences, front-loading the core purpose and key constraints. Every sentence adds value without 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?

Given the presence of an output schema, the description covers creation, idempotency, and a parameter nuance. Missing details like handling of inactive boards or full return behavior, but overall adequate for a creation tool with output schema.

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 description adds valuable context beyond the schema: it explains idempotency related to the name parameter and specifies when to use projectType (only when default is ambiguous). This compensates well for the schema's generic descriptions.

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 the tool creates a Huly board, uses specific verb and resource, and distinguishes itself from sibling create tools like create_board_card or create_channel by focusing on board creation.

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?

Provides clear when-to-use guidance and a specific condition for the projectType parameter. However, it does not explicitly mention when not to use this tool versus alternatives like update_board or list_boards.

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