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 enumerates action names. It does not disclose side effects, whether actions are destructive or reversible, required permissions, or what each action changes.

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 front-loads the action list with no filler. However, for a polymorphic tool with eleven parameters, this level of brevity leaves out critical structure such as per-action parameter requirements.

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 complex action-dispatch tool with eleven parameters, no annotations, no output schema, and no schema descriptions, the description is far too sparse. It names the actions but omits parameter mapping, behavioral detail, and routing guidance needed to invoke board_act correctly.

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 needs to compensate, but it only lists action values and notes that 'result' is required for done. It does not explain which of the other nine parameters apply to which action, or what fields like key, kind, item_id, event_id, parent_id, and waiting_for mean.

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 identifies the tool as handling 'Board actions' and lists the supported action names, which gives a basic sense of its role. However, it does not clarify what a 'board' is here, what each action operates on, or how this differs from the sibling board_list tool.

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?

There is no guidance on when to use board_act versus board_list or any other sibling, nor on how to choose among the listed actions. The only constraint-like note is '(result required)' for done, which is a requirement rather than usage guidance.

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