generate_hreflang

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

No annotations are available, so the description carries the full burden. It discloses a critical behavior: if any listed page lacks the full set or self-reference, the entire cluster is ignored, which is a key failure condition. It does not describe the output format or edge cases, but that is partially covered by the output 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?

The description is two sentences long, front-loaded with the tool's purpose, and every sentence adds substantive information. There is no padding or repetition.

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 tool's simplicity and the existence of an output schema, the description is largely complete. It covers the core input requirements and the critical cluster-ignored behavior. Minor omissions like URL formatting (absolute vs relative) and the effect of include_x_default are acceptable given the schema and parameter naming.

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 schema has 0% description coverage for parameters, so the description must compensate. It adds meaning to the 'pages' parameter by specifying that each page requires 'lang' and 'url', which is essential. The 'include_x_default' parameter is left unexplained, though its name is self-explanatory, so the compensation is partial.

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's function ('Generate hreflang link tags') with a specific verb and resource, and it is distinct from sibling tools like generate_meta_tags or generate_robots_txt. It also specifies required input fields, further clarifying its purpose.

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 does not explicitly compare this tool to alternatives or state when to use it over siblings. However, it provides clear context that each page must include 'lang' and 'url' and that the full set with self-reference is required, which guides correct usage. No exclusions or alternative tool mentions are present, so it falls short of explicit guidance.

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