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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description still adds real value by enumerating what the call does NOT do (execute targets, generate fictional runs, require Tools/checks), clarifying it is a pure static check.

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?

Two short, front-loaded sentences with zero filler; the core action leads and the scope exclusions follow immediately.

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?

There is no output schema, so the description should convey what validation returns (pass/fail, error list, codes), and it should point to how a recipe is constructed. Neither is present, leaving the agent unable to interpret results or build the input for this non-trivial nested-object tool.

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 single 'recipe' parameter is an opaque freeform object with 0% schema description coverage, and the description says nothing about its expected fields, shape, or where to find the recipe schema (e.g. firedrill_schema). With an open nested object and no compensating detail, the agent is left guessing what a valid recipe looks like.

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 (validate) and resource (repository-owned simulation recipe object) with the scoping qualifier 'before admission', so an agent can distinguish it from execution-oriented siblings like firedrill_materialize. It stops short of explicitly naming an alternative tool, but the purpose is unambiguous.

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?

'Before admission' implies the lifecycle stage at which this should be called, which is genuine usage context. However, no alternative is named and no explicit when-not condition is given beyond the general 'does not execute targets' scope note.

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