hyperframes_validate

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

No annotations exist, so the description carries the full burden — and it omits the key behavioral question: does validation mutate the project? The presence of an 'overwrite' parameter ('Explicitly allow replacing existing media') implies possible write behavior that the description never acknowledges. It also says nothing about strictness, failure modes, or whether it blocks rendering.

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?

One purpose sentence followed by an args block; front-loaded and free of filler. The Args block partially duplicates the schema, but the whole definition is short enough that this costs little.

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?

An output schema exists, so return values needn't be described. But for a validation tool with no annotations, a puzzling write-related parameter, and many similar sibling checkers, the definition does not give an agent enough to call it confidently or in the right order.

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 supplies the one piece the schema lacks for the required parameter ('Absolute path to the Hyperframes project directory'), which compensates for the 50% coverage. However, it adds nothing about 'overwrite' — the schema documents it but the description never explains why a validation tool accepts a media-replacement flag, leaving a genuine semantic gap.

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?

States a specific verb and resource plus a scope ('Validate a Hyperframes project for rendering readiness'), which is clearly distinguishable from render/preview tools. It does not, however, distinguish itself from close siblings like hyperframes_doctor, hyperframes_inspect, or video_preflight, which plausibly do overlapping checks.

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?

There is no explicit when-to-use, no prerequisites, and no named alternative. 'For rendering readiness' only weakly implies it runs before hyperframes_render; the agent is left to infer sequencing and whether doctor/preflight should run first.

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