Audit Drawing

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

The description mentions 'fix errors', implying modification, which is consistent with readOnlyHint=false. However, it fails to disclose specifics such as what errors are detected, how fixes are applied, whether the operation is reversible, or any side effects beyond the annotation.

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 a single sentence of 11 words, which is concise but overly minimal. It sacrifices valuable details that could improve usability, such as behavioral context or output schema hints.

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?

Despite having an output schema, the description only hints at the tool's purpose. It lacks details about the audit process, error types, or result interpretation, making it incomplete for a tool with potentially complex behavior.

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?

There are no parameters (0 params), and schema coverage is 100%. Per guidelines, baseline for 0 params is 4. No additional parameter information is needed.

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 runs an integrity audit on the drawing to detect and fix errors, with a specific verb and resource. However, it does not distinguish from similar sibling tools like 'validation_check' or 'drawing_critique', which may cause confusion.

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 no guidance on when to use this tool versus alternatives. No exclusions, prerequisites, or context for appropriate usage are given, leaving the agent without decision support.

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