amulen_create_board

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

Annotations already disclose that this is a non-readOnly, open-world, non-destructive operation. The description adds useful behavioral context about how bolsa_horas and horas_totales switch the board to an hour-budget mode, but it does not state permission requirements, side effects, or what happens if the project does not exist.

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?

Two sentences with no wasted wording. The core purpose is front-loaded, followed by the special hour-budget condition.

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 four-parameter creation tool with annotations present, the description covers the purpose and one special parameter interaction. It is still incomplete because required parameters and prerequisites are not documented, and no return behavior is described, though no output schema exists to cover that gap.

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 0%, so the description must compensate. It partially clarifies the relationship between bolsa_horas and horas_totales, but leaves the required project_slug and nombre parameters unexplained, and does not describe the types or expected values of any parameter.

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?

States a specific verb and resource: 'Create a board in a project.' It also explains that bolsa_horas plus horas_totales produces an hour-budget board. However, it does not explicitly differentiate this from siblings such as amulen_list_boards or amulen_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?

Provides no explicit guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. The only conditional guidance is about the hour-budget variant, not about when creating a board is appropriate.

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