Create Board

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

With no annotations, the description carries the full behavioral burden, but it only restates the high-level creation action. It does not disclose side effects, permissions, idempotency, or any constraints, leaving the agent without meaningful behavioral transparency.

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 a single short sentence that states the core purpose with no filler and is easy to parse. While concise, it is too sparse to convey the missing parameter and usage guidance, making it efficient but not fully informative.

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 create tool with three parameters and no annotations, the description is incomplete. It fails to explain the meaning of projectId, name, or position, and does not mention prerequisites, even though an output schema exists to cover return values.

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 has 0% description coverage and the description mentions none of the three parameters. An agent receives no help understanding that projectId references the parent project, name is the board title, or that position controls ordering, so the description adds no value beyond the raw 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?

The description 'Create a new board in a project' clearly identifies the action (create), resource (board), and scope (project). It distinguishes from sibling tools by resource name, though it does not explicitly contrast with alternatives like create_project or create_list.

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?

No guidance is provided about when to use this tool versus alternatives such as create_project or get_boards. It lacks prerequisites, such as requiring an existing project, and does not mention when this tool should be preferred over sibling create tools.

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