Create board

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

No annotations are present, so the description must disclose behavioral traits. It only states 'Create board', which is minimal. It does not mention that this is a write operation that requires a projectId, nor any side effects, permissions, or limitations. The description adds little beyond the name.

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 very short and to the point, but it lacks structure. It is not front-loaded with the most important information, and it does not earn its keep by providing much value beyond the tool name. A single sentence is acceptable if comprehensive, but here it is insufficient.

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 low complexity (1 parameter, no output schema, no annotations), the description is still incomplete. It does not explain what creating a board entails, what the response looks like, or how it fits into the larger system. The agent would need to infer much from the schema alone.

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 includes property descriptions for 'name' and 'projectId', so the base coverage is provided. However, the tool description does not add any additional meaning or advice about these parameters. It doesn't explain how to use the body object or any constraints beyond what is in the 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 clearly states the verb 'Create' and the resource 'board', and includes the HTTP method and endpoint. It is straightforward, but does not differentiate from other create tools like 'weeek_create_project' or 'weeek_create_board_column'. However, the name itself is specific enough to avoid confusion.

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 guidelines are provided about when to use this tool versus alternatives. There is no mention of prerequisites, context, or exclusions. The agent is left without guidance on whether this is the right tool for a given scenario.

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