drawing

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

Annotations indicate readOnlyHint=false, but the description does not disclose potential side effects, required permissions, or failure modes for operations like 'save', 'purge', or 'undo'. Behavioral traits beyond the annotation are minimal.

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 front-loaded with 'Drawing file management' and uses a clear bullet list of operations. It is concise with no unnecessary words, but the structure could be improved by grouping operations or using consistent formatting.

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 multiple operations and presence of an output schema, the description adequately lists operations and their data inputs. However, it lacks details on return values for each operation and does not explain how to handle common scenarios like opening a non-existent file. It is functional but not exhaustive.

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 input schema has 0% description coverage, so the description partially compensates by showing expected data fields per operation (e.g., 'data: {name?}' for create). However, the 'data' parameter is loosely defined as any object, and the description does not fully cover all operations or parameter constraints.

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 lists specific operations (create, open, info, etc.), making it distinct from sibling tools which focus on annotations and PID. The verb+resource pattern is explicit.

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 lists all operations with brief explanations, providing clear context for when to use each sub-operation. However, it does not explicitly contrast with sibling tools or state when not to use this tool. The distinction is implied by the operations offered.

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