Generar prompt de página web para Claude Code

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions using 'datos reales' and 'mejores reviews' but does not explain whether the tool fetches external data, has side effects, or requires authentication. The description is insufficient for an agent to understand the tool's operational behavior.

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 with no wasted words. Every sentence adds value: the first states the core function, the second clarifies the intended use case. It is front-loaded and efficient.

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?

For a tool with 4 parameters and no output schema, the description provides enough context to understand the purpose but does not explain the return format (a prompt string) or how the tool integrates with the data sources. It is minimally adequate but leaves gaps in a complete mental model.

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 coverage is 100% and all parameters have descriptions in the schema. The tool description does not add additional meaning beyond the schema, except for implying that 'max_reviews' relates to 'mejores reviews'. Baseline 3 is appropriate since the schema already documents the parameters adequately.

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 verb (Genera), the resource (prompt para Claude Code que construye una landing page), and the target (venderle al negocio). It is distinct from sibling tools, which are search and retrieval tools, not generation tools.

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 explicitly says the tool is 'Pensado para venderle la página al negocio', implying when to use it. However, it does not explicitly contrast with siblings or state when not to use it. The context is clear enough for an agent to differentiate from data retrieval tools.

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