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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuine value by disclosing the return contract — "ok or the list of issues with their paths" — which is important since there is no output schema. It doesn't say how deep the validation goes (syntax vs schema conformance, which would relate to liquid_schema), leaving a behavioral gap.

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?

A single compact sentence with the action front-loaded and the return behavior appended after the semicolon. No filler or restatement of the title.

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?

Return format and the read-only nature are covered, which is most of what a simple validator needs. However, with a completely untyped parameter and no output schema, the description should at minimum state what `recipe` accepts and what kinds of issues are reported; that gap leaves the tool under-specified.

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 is one required parameter with 0% schema coverage and an empty schema definition (`"recipe": {}`), so nothing tells the agent whether to pass a file path, an identifier, or the recipe body itself. The phrase "without opening it" hints it is not a handle, but the description never clarifies the expected shape or format of `recipe`.

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?

"Check a recipe" gives a specific verb and resource, and "without opening it" implicitly distinguishes it from the sibling liquid_open (which loads/opens). An agent can tell it apart from liquid_open, though liquid_schema is never addressed, so sibling differentiation is only partial.

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?

"Without opening it" implies the usage context: check validity cheaply before loading. But there is no explicit when-to-use/when-not statement, no mention of when to prefer liquid_open or liquid_schema, and no prerequisites or error conditions described.

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