Draft a title and meta description

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

With no annotations provided, the description carries the behavioral disclosure burden. It explains what the tool collects, mentions the conditional Search Console data, and states the actual output—evidence and length limits—rather than a finished draft. This gives the agent a clear picture of what to expect.

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 dense sentence that packs in the tool's inputs, conditional behavior, and output type without unnecessary filler. It is front-loaded with the core purpose and remains readable, though it could be split into two sentences for slightly better clarity.

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 is largely complete for a read-oriented tool: it specifies what data is gathered, the Search Console condition, what the return value contains, and the division of labor between the tool and the user. It does not detail the exact structure of the returned evidence, but this is not critical given the absence of an output schema and the focused scope.

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 input schema already documents all three parameters with 100% coverage, including url, keyword, and variants. The description adds context about the page content elements used, but it does not materially enhance the schema's parameter explanations, so the baseline score of 3 is appropriate.

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 a specific verb and resource: it 'collects everything needed to write a strong title tag and meta description,' including current tags, headings, opening prose, and Search Console queries. This distinguishes it from sibling tools like audit_page or serp_preview, which serve different purposes.

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 implies that this tool is used when gathering evidence for drafting title tags and meta descriptions, and explicitly notes that the user writes the copy, not the tool. However, it does not name any alternative tools or provide explicit when-to-use versus when-not-to-use guidance.

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