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

Annotations provide readOnlyHint=false and destructiveHint=false, indicating a mutation but not destructive. The description adds critical behavioral details: it requires editToken and latest revision, and it clarifies that the viewer's theme is not part of drawing JSON. This informs the agent about prerequisites and side effects beyond the basic mutation hint.

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 concise, with two sentences and a clear list of affected attributes. The atomicity requirement is mentioned upfront, and the theme clarification is placed at the end as a minor, non-essential note. It is not overly verbose, but could be slightly more structured to separate the key purpose from the nuance.

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?

The tool is complex with nested objects and 6 parameters, but the schema covers all parameter semantics comprehensively, and the description covers the behavioral nuances (atomicity, token/revision requirements, theme exclusion). Since there is no output schema, the description doesn't need to explain return values. The tool is relatively complex but the combination of description and schema is sufficient for correct invocation.

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 the schema already explains all parameters in detail, including the camera constraints, revision staleness, and editToken security. The description adds a brief mention of atomicity and the theme exclusion, but for most parameters it adds little beyond the schema. Since coverage is high, a baseline of 3 is appropriate.

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 states a specific verb ('set'), the resource ('drawing'), and lists the specific properties that can be modified: title, camera, and active drawing color. It also emphasizes the atomic nature of the operation, distinguishing it from other drawing tools. The tool name and title reinforce this but the description adds clarity.

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 implies usage when needing to change drawing properties, and the atomic mention hints at batching changes. It does not explicitly mention when not to use this tool or alternatives, though sibling tools like get_drawing and create_drawing suggest alternatives. The context signals show openWorldHint=true, but the description doesn't explicitly guide against usage in read-only contexts, though it does require editToken which implies mutation.

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