list_websites

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions that the tool lists websites 'with llms.txt files' but doesn't describe what 'known websites' means, whether this is a read-only operation, what format the output takes, or any limitations (like pagination or rate limits). The description is minimal and lacks important behavioral context.

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 extremely concise - a single sentence that directly states the tool's purpose. There's zero waste or unnecessary elaboration. It's appropriately sized for a simple listing tool with well-documented parameters.

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?

For a simple listing tool with 100% schema coverage but no annotations and no output schema, the description is adequate but has clear gaps. It explains what the tool does but doesn't provide context about what constitutes 'known websites' or what the output format will be. The description meets minimum viability but could be more complete.

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 schema already documents both parameters (filter_llms_txt and filter_llms_full_txt) with clear descriptions. The description doesn't add any parameter semantics beyond what's in the schema - it doesn't explain how these filters work together or their default behavior. Baseline 3 is appropriate when schema does the heavy lifting.

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's purpose: 'List known websites with llms.txt files' specifies both the action (list) and resource (websites with llms.txt files). However, it doesn't explicitly differentiate from the sibling tool 'check_website', which likely serves a different purpose (possibly checking individual websites rather than listing them).

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 no guidance on when to use this tool versus alternatives. There's no mention of the sibling tool 'check_website' or any context about when listing websites is appropriate versus checking individual ones. The description simply states what the tool does without usage context.

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