Validate Editor Runtime Contract

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

No annotations are provided, so the description must fully disclose behavior. It only mentions validation of HTML/JS but omits what happens on failure, side effects, or whether it modifies state. This leaves significant gaps for a validation tool.

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 concise sentence that quickly conveys the core purpose. It avoids fluff and front-loads the key action and resource. Minor improvement could include structured bullets, but it's effective.

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 lack of output schema and presence of complex nested objects (entry, sections), the description fails to explain return values, error reporting, or validation outcomes. This is critical for a validation tool and leaves the agent underinformed.

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 documents parameters. The description adds no additional meaning beyond the schema, achieving the baseline. It does not clarify usage of nested objects or secrets handling beyond the schema's own descriptions.

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 validates 'Advanced Editor runtime HTML/JS' and is used 'before save or publish', giving a specific verb and resource. However, it does not explicitly distinguish from sibling tools like dl_validate_object, though the niche is implied by the name.

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 'before save or publish' but provides no explicit guidance on when not to use, prerequisites, or alternatives. For a validation tool, more context on invocation timing would help.

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