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

With no annotations provided, the description bears full burden. It states 'Extract content' but does not disclose whether it extracts the entire page, only the main content, or how images are handled. There is no mention of rate limits, authentication needs, or output format details beyond Markdown.

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 concise at one sentence with no waste. However, it is slightly too sparse; a brief additional note on scope would improve structure without harming conciseness.

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 simplicity (2 params, no output schema), the description lacks completeness. It does not explain what constitutes 'content' (e.g., full HTML vs main text), whether images are included by default, or error handling. More context is needed for reliable agent usage.

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 50% (only url has a description). The description does not add meaning beyond the schema for 'url' and ignores 'include_images' entirely, failing to compensate for the missing schema description.

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 action (extract content) and the output format (Markdown), which effectively communicates the tool's purpose. It distinguishes from sibling tools like agentseo_content_brief or agentseo_content_gap, as those involve content generation rather than extraction.

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?

There is no guidance on when to use this tool versus alternatives. For instance, if the user wants to extract content for SEO analysis, this tool is appropriate, but no context is provided about prerequisites or scenarios where other tools (like agentseo_page_cro_qa) might be more suitable.

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