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

With no annotations, the description carries the full burden; it does disclose the key behavior that a persistent, shareable resource is created and that the returned link is meant for the user to observe and download. It does not say whether calling twice creates two separate boards, how long the board lives, or whether any auth/ownership applies.

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 short sentences, front-loaded with the action and then the follow-up contract. No filler, no redundancy.

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 single-parameter creation tool with no output schema, it covers what is created, what comes back (a link), and what the agent should do with it. The remaining gap is lifecycle behavior — repeated calls and whether one board per session is expected — but nothing critical to invoking it correctly is missing.

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?

Only one parameter exists and schema description coverage is 100% with an enum of doodle/html/markdown, so the schema already fully specifies it. The description never mentions the 'kind' choice or what each board type implies, adding no meaning beyond the schema — the baseline 3 applies.

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 ('Open a new, empty board') plus the side effect of returning a link, which is enough to distinguish it from the read/write/edit siblings. It does not explicitly name those siblings, so it stops short of full differentiation.

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?

Usage is implied by the workflow instruction ('Give the link to the user: they watch your work there'), which tells the agent what to do after the call. However, there is no guidance on when to choose open_board versus going straight to write_board or draw on an existing board, and no exclusions.

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