drawing

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

The annotation readOnlyHint=false already signals this is a read/write tool. The description adds a concrete list of operations but doesn't disclose behavioral nuances such as side effects on the current drawing, file system changes, or reversibility beyond the operation names themselves. It's adequate but not deeply transparent.

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 efficiently structured as a bulleted list of operations, with each line providing a clear verb and optional data parameters. It's front-loaded with a one-line summary and avoids unnecessary prose.

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?

Given the tool's many operations, the description covers each one's core purpose and data inputs, and includes special cases like QSAVE. It lacks details on prerequisites (e.g., whether a drawing must be open) and the incomplete `include_screenshot` flag, but overall it's reasonably complete.

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?

The description goes beyond the schema by documenting the expected `data` structure for each operation (e.g., `{path}` for open, `{name?}` for create), which greatly helps parameter usage. However, it doesn't mention the `include_screenshot` parameter and uses an ad-hoc notation rather than aligning with the schema properties.

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 clearly states 'Drawing file management' and enumerates specific file-level operations (create, open, save, export, plot, purge, undo, redo), distinguishing this tool from sibling tools that focus on layers, entities, blocks, etc.

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 groups operations under a single tool with a clear file-management scope, but it never explicitly states when to use this tool versus sibling tools like `layer` or `entity`. The usage is implied by the operation list, not directly stated.

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