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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds concrete behavioral details: it issues HTTP GET requests for live URLs and reads local files without modifying them. This extends the annotation information with specific network and file access behavior, which is valuable 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?

The description is well-structured with clear sections (main purpose, USAGE GUIDELINES, BEHAVIORAL TRANSPARENCY). It front-loads the core purpose and is not overly verbose. Minor redundancy exists (e.g., 'Read-only data extraction' appears both in the main text and the behavioral section), but overall it is efficient and scannable.

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 single-page extraction tool, the description is complete: it lists the exact metadata extracted, gives usage boundaries, and covers behavioral notes. There is no output schema, but the list of extracted items gives sufficient context. It does not describe the output format in detail, but that is not critical for tool selection and invocation.

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 100% for both parameters. The description does not add any additional meaning beyond what the schema already provides for 'target' and 'pageType'. It restates the same information (e.g., live URL or local file path) without further nuance. Baseline 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 the tool crawls a live URL or parses a local HTML/template file to extract a specific list of SEO metadata (Title, Meta Description, Headings, etc.). It uses a specific verb ('Crawls') and resource, and distinguishes itself from specialized audits by noting it is for extraction before running them.

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 usage guidelines are provided: use for single-page metadata extraction, do not use for multi-page batch crawling (explicitly names seo_audit_sitemap_multipage), and do not use for framework discovery (names seo_discover_project). This gives clear when-to-use and when-not-to-use with alternatives.

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