check_title_meta

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

With no annotations, the description carries the full burden. It usefully discloses the output shape (a 0-100 score with fixes), but is silent on how items are processed (e.g., whether urls are fetched or only provided title/meta are analyzed), batch behavior, or any auth/rate limits, leaving meaningful behavioral gaps.

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?

Two tight sentences, front-loaded with the check criteria and closed with the return summary. No filler, though it stops short of a genuinely efficient 5 by omitting any routing or scoping clause.

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 structured-input tool with no output schema and no annotations, the description covers purpose and rough return value but leaves parameter semantics and usage context unaddressed. Adequate but with clear gaps relative to the tool's complexity.

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 0% on a nested array-of-objects parameter (title required; url, meta, keyword optional; max 100 items). The description adds no parameter meaning at all, so an agent must infer the required title field and the 100-item cap purely from the raw 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 (Check) and resource (title tags and meta descriptions) plus the concrete criteria examined: length/pixel truncation, keyword placement, CTR hooks. This is clearly distinguishable from siblings like cluster_keywords or content_brief_outline, though it never explicitly names an alternative.

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 an SEO meta-audit but gives no when-to-use, when-not-to-use, or alternative guidance. It does not say whether to call this before or after content_brief_outline, or how it relates to the other SEO siblings.

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