extract_metadata

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

Annotations already mark the tool as readOnlyHint and idempotentHint, so the description's main behavioral contribution is listing the exact metadata fields extracted (title, meta description, etc.), adding value beyond the annotations.

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 three sentences: purpose with listing, ideal use cases, and an example. It is front-loaded and every sentence adds value without redundancy.

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 no output schema, the description partially covers return values by listing extracted metadata items. It lacks details on format or structure but is sufficient for a simple extraction tool within a rich set of sibling tools.

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 schema already fully describes the url parameter (with format and description), so baseline is 3. The description does not add further parameter-specific semantics beyond the tool's overall purpose.

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 extracts SEO metadata (title, meta description, Open Graph tags, canonical URL, schema.org data) with a specific verb 'extract' and resource 'page's SEO metadata'. It distinguishes from siblings like fetch_url or extract_text by focusing on structured metadata.

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 explicitly says 'Use this when you need a page's SEO metadata' and suggests use cases (site audits, competitive SEO analysis). It does not explicitly exclude other tools or mention when not to use, but provides clear context.

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