seo_title_description_length_checker

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

Annotations already provide readOnlyHint, destructiveHint, idempotentHint; description adds 'Runs locally on the text you provide (read-only, non-destructive, contacts no external service)' and rate limit of 30 requests per minute for anonymous callers. No contradiction and adds meaningful context.

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?

Description is thorough but slightly lengthy; however, every sentence earns its place by adding purpose, usage, behavioral notes, or parameter semantics. It is well-structured and front-loaded.

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 complexity (6 parameters, output schema exists), the description covers purpose, usage context, behavioral traits (read-only, rate-limited), parameter details, and output structure. It is fully complete for an agent to decide and use correctly.

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% with descriptions for all 6 parameters. Description adds value by explaining the pixel width estimation (Arial font sizes), the purpose of brand and brandSuffix parameters, and details of the output (chars, words, pixel width, truncation point, score, warnings, suggestions). This goes beyond 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?

The description clearly states the tool analyzes title and meta description lengths against Google SERP pixel limits, with specific verb 'analyze' and resource 'HTML title tag and meta description'. It differentiates from sibling tools seo_meta_tag_generator and seo_keyword_density_checker by explicitly stating what each does.

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?

Explicit guidance on when to use ('audit or proof an existing snippet before publishing') and when not to (for building tags, use seo_meta_tag_generator; for body content, use seo_keyword_density_checker). Also notes rate limiting and read-only nature.

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