yougile_create_board

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

Annotations already indicate readOnlyHint=false and destructiveHint=false, which are consistent with the description. However, the description adds no behavioral context beyond what annotations state—no mention of permissions, idempotency, side effects, or error behavior. It briefly adds the 'inside a project' scoping, but that is structural rather than behavioral.

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 sentence with no redundant words. It is appropriately sized and front-loaded with the key verb and resource. Every word earns its place.

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 create tool with two well-documented parameters, the description is minimally adequate. However, it lacks mention of return value, expected permissions, or behavior on invalid projectId. While no output schema exists, the description does not compensate by explaining what the agent can expect from the tool's result.

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% (both 'title' and 'projectId' have explicit descriptions). The description adds no further meaning; it merely restates the schema's parameters without any additional detail about their semantics or usage.

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 is specific: 'Create a new board inside a project.' It names the verb ('create') and the resource ('board'), with a clear location constraint ('inside a project'). This distinguishes it from siblings like yougile_update_board, yougile_list_boards, and yougile_get_board.

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 for when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or explicitly reference sibling tools. Usage is only implied by the verb 'create'.

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