parse_page

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

The description adds substantial behavioral detail beyond annotations: it mentions the underlying Crawl4AI POST /crawl call, explains proxy configuration and egress IP implications, and lists return fields including `truncated` and `used_proxy`. This significantly enriches the agent's understanding of what the tool does.

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 the purpose first, then a proxy detail paragraph, then a return-fields list. Every sentence adds value, though the technical reference to 'Crawl4AI POST /crawl (0.8.x)' is a minor extra that could be trimmed. Still, it remains appropriately concise.

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 description covers the tool's behavior, return format, proxy handling, and timeout behavior, making it nearly complete for a network-fetch tool with annotations and a high-coverage schema. It does not mention explicit alternatives or edge-case errors, but the output schema and annotations fill remaining gaps.

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%, so the baseline is 3. The description adds extra meaning by explaining the proxy override behavior ('overrides server default_proxy when non-empty') and the timeout clamping ('clamped to server max'), which goes beyond the schema descriptions.

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 opens with a specific verb and resource: 'Fetch a web page via Crawl4AI and return cleaned markdown JSON.' This clearly distinguishes the tool from the sibling `check_upstream`, which appears to be a different operation (likely a health check).

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 provides operational context (proxy behavior, return fields) but does not explicitly state when to use this tool versus alternatives like `check_upstream`. Usage is implied by the purpose but lacks explicit directional guidance.

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