art.canvas.get_state

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

With no annotations, the description must carry the burden of behavioral disclosure. It does indicate a read-only enumeration by saying 'Get' and mentions both output forms, but it does not disclose possible session requirements, failure behavior, or side-effect-free guarantees beyond the verb itself.

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 description is one sentence, front-loaded with the action and resource, and every clause adds value. It avoids restating the tool name or adding irrelevant context.

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?

This is a low-complexity read tool with fully documented parameters and clear return output formats in the absence of an output schema. It could be slightly more complete by noting that the state belongs to a specific canvas session and what happens if that session is missing, but nothing essential is absent.

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%, and the description does not add meaning beyond what the input schema already says. format and session_id are both documented structurally; the description's mention of 'color map' and 'base64 PNG' mirrors the schema enum.

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 ('Get the current canvas state') and names the exact return representations, so it is easily distinguishable from sibling getters like art.canvas.get_pixel. No ambiguity about what object is being read.

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 description gives no guidance on when to use this tool versus alternatives such as art.canvas.get_pixel, art.canvas.save, or art.canvas.analyze_ref. The context is only implied by the word 'current', with no exclusions or alternative routing.

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