create_drawing

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

With no annotations provided, the description carries the transparency burden. It discloses that the drawing is temporary and not persisted to disk until save_drawing is called, which is key behavioral information. It does not mention potential side effects like becoming the active drawing, but the core behavior is well covered.

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 two short sentences, front-loaded with the main action, and every sentence adds value. The note about save_drawing is essential and succinct.

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?

For a simple tool with an output schema, the description covers the temporary nature and save requirement. However, the unexplained 'name' parameter leaves a gap in the tool's usage contract. Since the tool is simple and the query about the name is minor, completeness is adequate but not strong.

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 one optional parameter 'name' with a default, but no schema description and the tool description does not mention this parameter at all. With schema coverage at 0%, the description needed to explain the purpose of 'name' (presumably a drawing name), and it fails to do so, leaving the agent to guess.

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 the tool creates a new, empty drawing ('Crea un dibujo nuevo y vacio'), which is a specific verb+resource with the scope 'nuevo y vacio' distinguishing it from open_drawing, read_drawing, or create_working_copy. It also notes the temporary nature, adding further specificity.

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 provides usage context by explaining the drawing is temporary and must be saved with save_drawing(path). This implies when to use the tool (creating a new drawing) and directs the user to a follow-up action, though it does not explicitly exclude alternatives like open_drawing.

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