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

Annotations already declare readOnlyHint/idempotent/non-destructive, so the bar is lower; the description still adds real behavior: pagination via next_offset, short-lived preview link expiry, and that the call is free. Those are traits the annotations cannot express.

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?

Front-loads the return contents, then pagination, then cross-tool link reuse. One long first sentence is dense but every clause carries information; no filler.

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?

With no output schema, the description correctly carries the burden of describing return values and does so in detail, including pagination semantics. Only the exact shape of the 'outline' and preview link lifetime is left vague.

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%, so canvas_id, limit and offset are already documented in the schema. The description reinforces the offset/next_offset round-trip but adds little that the schema doesn't already state, so 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 ('Read one of the user's canvases') and immediately enumerates what is returned: name, groups, card outline fields, links. An agent can distinguish it from list_canvases or open_canvas purely from this text.

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?

Gives concrete downstream guidance: 'pass next_offset as offset to read more', 'Reuse the popnow:// links as inputs for other PopNow tools, and the card ids for add_to_canvas.' It does not explicitly say when to prefer this over list_canvases or open_canvas, but the operational context is clear.

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