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

With annotations already declaring destructive=false, idempotent=true and openWorld=false, the description adds real context: cost ('Free'), pagination behavior for chats, and the range of item types returned. It never clarifies the tension between the intuitive read-only nature of 'get content' and the readOnlyHint=false annotation, nor return size/limits, so it earns a 4 rather than a 5.

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 usage trigger and closes with the exclusion, with no filler sentences. The middle enumeration of item types is long but each entry carries selection-relevant information, so it is appropriately sized rather than padded.

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?

There is no output schema, so the description usefully enumerates what content forms come back and how to page chats. It does not cover permission/auth needs or any limits on how much content is returned, which is a minor gap for a read tool whose sibling xcut_get_canvas handles listing.

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 100%, so canvas_id, item_id and before are already documented in the schema, including the ordering provenance ('from xcut_get_canvas') and the chats-only pagination semantics. The description's 'by canvas id and item id (from xcut_get_canvas)' and 'paginate with `before`' largely restate that, 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 (get the full content), the resource (an item on the XcutAI canvas), and enumerates the content variants it returns (transcript/stats, note, chat, website, analytics table, Meta ad, group). It explicitly distinguishes itself from xcut_get_canvas, so an agent can route without opening either 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?

Gives an explicit trigger ('Use this when you need the full content of an item') and an explicit exclusion with the alternative ('Do not use to list a canvas (use xcut_get_canvas)'). Nothing about when to select this tool versus its closest sibling is left to inference.

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