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

The annotations already indicate readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds useful behavioral context by explaining that it returns clean, structured content in multiple formats and that it targets general extraction use cases. It does not contradict 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 two concise sentences with no filler. It front-loads the core action and resource, then states the outputs and use cases. Every sentence adds useful information.

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?

The input schema is rich and fully covers parameter semantics, the annotations cover safety and idempotency, and an output schema exists. The description adds the missing usage context and high-level output expectations. It is slightly incomplete in not guiding the agent toward sibling tools for narrower extraction needs, but overall it is sufficient for correct 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%, and the parameters already have detailed descriptions including enums, defaults, and credit implications. The tool description does not add parameter-level meaning beyond what the schema provides, so it meets the baseline without exceeding it.

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 uses a specific verb and resource ('Extract clean content from a webpage') and lists the expected outputs (Markdown, metadata, links, schema, sections), which makes the tool's purpose clear. It does not explicitly distinguish this comprehensive extractor from the sibling tools like tooltrace_links or tooltrace_schema, but the broad output list implies it is the general-purpose option.

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 states when to use the tool: 'Use this for scraping, RAG ingestion, or content analysis.' However, it does not mention when not to use it or point to the more specialized sibling tools for link-only, metadata-only, or schema-only extraction.

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