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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine beyond-annotation context: the sort order (newest first, pinned first), the durability of the rows ('stay on the market page until deleted'), and that no authorization is required for any market address. It does not discuss page-boundary behavior (e.g., how pinned items interact with paging), which is the only remaining behavioral gap.

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?

Three short sentences, each doing distinct work: what it lists, how it differs from the ephemeral sibling, and who can call it. The defining contrast is front-loaded immediately after the purpose, and there is no redundant restatement of the tool name or schema fields.

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 simple filtered-list tool with only four parameters, an output schema present, and strong annotation coverage, this is complete: purpose, ordering, durability, access model, and sibling differentiation are all stated. Return shape and paging parameter details live in the schema, so nothing an agent needs to invoke 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?

Schema coverage is 75%, with marketAddress carrying no schema description; the description's 'any market address works' supplies the missing meaning for that required parameter (permissionless lookup). chainId and the limit/offset paging parameters are already fully documented in the schema, so no further expansion is needed. This is modest but real added meaning above the schema baseline.

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 gives a specific verb and resource ('List a market's persistent creator canvas updates') plus ordering semantics ('newest first, pinned first'). It explicitly distinguishes this from the sibling problee_publish_market_surface by contrasting durable rows with the ephemeral live surface, so an agent can pick the right tool without opening a schema.

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?

It establishes the usage context clearly: read durable canvas updates for a market, and it clarifies the access model ('Public read — any market address works'), which removes a common pre-check. It stops short of explicit when-to-use/when-not routing (e.g., pointing to problee_delete_canvas_update or problee_post_canvas_update for write operations), so it is clear context rather than full guidance.

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