roiq_create_whiteboard

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

No annotations provided. Description mentions creation and provisioning but lacks details on permissions, side effects, or response behavior. Does not disclose whether the operation is idempotent or destructive.

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?

Single sentence, front-loaded with action. Slightly verbose with 'y la provisiona en el backend del board', but still compact.

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?

Minimal description for a simple 2-parameter tool. Lacks information about return values or error states. Acceptable but not thorough.

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 coverage is 0%, so description must compensate. It mentions 'space' implicitly but does not explain the format or constraints for either parameter (e.g., title uniqueness, space identifier).

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?

Description clearly states the tool creates a whiteboard (ROIQ Board) in a space and provisions it. Verb+resource are specific, and it distinguishes from sibling tools like roiq_create_page or roiq_create_db.

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 on when to use this tool versus alternatives. Does not specify prerequisites or when not to use it.

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