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

Annotations already establish readOnly/idempotent/non-destructive, so the description goes further and adds genuinely new behavior: zero credit cost, an explicit auth requirement (OAuth via host prompt or an 'Authorization: Bearer acd_live_…' header), and the non-obvious fact that rendering generation cards are re-checked against their jobs on every read.

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 functional payload is front-loaded in the first two sentences with no filler, and the behavioral notes follow logically. The auth/API-key boilerplate is lengthy and partly host-handled, but it is actionable information for an agent encountering an unauthenticated server.

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 read tool with an output schema already defining the return shape, the description covers purpose, cost, freshness semantics, and authentication. An agent has everything needed to decide to call it and to satisfy auth on first use.

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 100% and the single canvas_id parameter is already documented in the schema with its source (list_canvases or create_canvas). The description adds no format or constraint detail beyond that, so the baseline of 3 applies when the schema carries the load.

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 ('Read one board in full') and enumerates exactly what the read returns: cards with type/position/size/data, edges, and revision. This cleanly separates it from list_canvases, which returns a collection rather than a full 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?

The phrase 'Read one board in full' implicitly positions this against list_canvases for the summary case, and the note that card ids come from list_canvases/create_canvas gives context. However, it never explicitly names an alternative tool or states when not to use this one, so the routing guidance is inferred rather than stated.

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