web_seo_check

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

No annotations provided, yet description fails to disclose safety profile (read-only vs destructive), whether it follows redirects, rate limiting, or response format. Only lists analyzed elements without explaining what 'analysis' entails.

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?

Single efficient sentence with zero waste. Front-loaded with verb and scope. Parenthetical list appropriately specifies coverage without verbosity.

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?

Adequate for a single-parameter tool. Lists analyzed elements which hints at output structure, but lacks output format detail or auth requirements given no output schema exists. Minimum viable completeness.

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 has 100% description coverage ('URL to analyze'), so baseline applies. Description adds no additional param context (examples, format constraints, validation rules) beyond what's in the 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?

Clear specific verb ('analysis') and resource ('webpage') with explicit scope listing what elements are checked (title, meta, headings, images). Distinguishes from sibling 'web_fetch' by specifying SEO-focused analysis versus general content retrieval.

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?

Provides no guidance on when to select this versus alternatives like 'web_fetch' or 'web_extract_links'. No mention of prerequisites (e.g., public URLs only) or when NOT to use.

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