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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds genuinely useful behavior: the recipe is carried in the URL fragment, so nothing is sent to a server on open. That privacy/transport trait is not derivable from annotations or schema.

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?

Three short sentences, front-loaded with the action and outcome, followed by the two facts an agent needs (no server transmission, image source restriction). No filler.

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?

The deeply self-documented schema carries most of the load and there is no output schema, so the description needn't explain the recipe shape. It could state the return form explicitly (e.g. that a URL string is returned) rather than only 'a link', which is the one small ambiguity.

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?

Top-level coverage is 0%, but nested properties are richly described in the schema, so the real gap is small. The description still contributes the critical constraint that images must be inline SVG or data: URLs — a restriction that matters for link-based delivery and is not stated at that level in the schema.

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: 'Turn a recipe into a link that opens the icon in Liquid Composer.' An agent can tell this apart from liquid_validate and liquid_schema by the outcome (a link, not validation or a schema), though the siblings are never named.

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?

Usage is implied by the outcome ('opens the icon in Liquid Composer') but there is no explicit when-to-use/when-not guidance and no routing between this and liquid_validate or liquid_schema. The agent must infer that this is the final hand-off step.

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