generate_seo_metadata_blueprint

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

With no annotations, the description must carry the full behavioral burden, but it only lists output types and gives no insight into side effects, validation rules, required permissions, or return format. It does not contradict annotations (none exist), but it omits critical behavioral context for a generation tool, such as whether it validates character limits or produces deterministic output.

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 a single, front-loaded sentence that efficiently lists all output categories. It avoids unnecessary words and directly communicates the core deliverable, though it could be slightly more structured with separate clauses for readability.

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 description outlines what is generated but does not clarify the shape of the output (e.g., a structured object, concatenated HTML, or separate strings) or any constraints like character min/max for meta descriptions. Given that the input schema is well-documented and no output schema exists, the tool would benefit from a note on how results are returned, making this minimally complete but not fully contextual.

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?

Schema description coverage is 100%, with every parameter already documented in the schema (e.g., page_title as 'Title of the page or web application'). The description adds no additional parameter meaning, so it rests at the baseline of 3 expected when the schema fully covers parameter semantics.

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 states a specific verb ('generates') and a detailed list of outputs (HTML head tags, OpenGraph, Twitter Cards, JSON-LD, sitemap metadata), making the tool's purpose crystal clear. It distinguishes itself from sibling tools like generate_seo_aeo_geo_blueprint by focusing narrowly on metadata generation rather than broader SEO strategy.

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?

No guidance is provided on when to use this tool versus alternatives. Sibling tools like generate_seo_aeo_geo_blueprint might overlap, but the description does not mention any selection criteria, prerequisites, or exclusions. The agent is left to infer usage from the name and description alone.

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