Parse Website

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

Annotations already indicate readOnlyHint=false, idempotentHint=false, and destructiveHint=false. The description adds that parsing produces chunks and that no knowledge base is required, implying the result is returned directly rather than persisted. However, it does not disclose potential side effects, whether the operation is stateless, or any cost/rate implications. Since annotations cover the safety profile, a score of 3 is appropriate.

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 a single, front-loaded sentence: 'Parse a website URL into chunks (no knowledge base required).' It delivers the core purpose and a key differentiator in under 10 words, with no filler or 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 the tool's moderate complexity (6 params, no output schema), the description provides a minimal but sufficient overview. It lacks details about return format, error behavior, or how this differs from the sibling lyzr_parse_website_apify. The schema covers parameter semantics, but the description does not fully contextualize the tool within the broader parse/knowledge-base workflow.

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 all six parameters are described at least at a basic level. The description itself does not elaborate on parameter meanings, but the schema already explains url, chunk_size, extra_info, extra_fields, chunk_overlap, and parser_config. No additional benefit is provided by the description beyond what the schema offers.

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 ('Parse'), the resource ('website URL'), and the output ('chunks'). It also distinguishes itself from knowledge base training tools via the parenthetical '(no knowledge base required)', which helps differentiate it from siblings like lyzr_kb_train_website. However, it does not explicitly mention other parse variants (e.g., lyzr_parse_text) or provide details on the exact nature of the chunks.

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 phrase 'no knowledge base required' implies a usage context: use this tool when you want to parse a website without storing the results in a knowledge base. This is a useful hint but not a full guideline. It does not explicitly state when to prefer this over lyzr_parse_website_apify or other parse tools, nor does it mention any prerequisites or exclusions.

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