fetch_test_site

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('fetch' and 'convert to markdown'), but does not disclose any behavioral traits such as network dependencies, error handling, rate limits, authentication needs, or what happens if the site is unavailable. This leaves significant gaps for a tool that likely involves external operations.

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, efficient sentence that directly states the tool's action and output format. It is front-loaded with the key information (fetching and conversion) and contains no unnecessary words or redundancy, making it highly concise and well-structured.

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 complexity of fetching and converting a website (which involves network operations and data transformation), the description is incomplete. There are no annotations, no output schema, and the description lacks details on behavioral aspects like error handling or output format specifics. This makes it insufficient for an agent to fully understand the tool's operation and potential issues.

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?

The tool has 0 parameters, and the schema description coverage is 100%, so there are no parameters to document. The description does not need to add parameter semantics beyond the schema. A baseline score of 4 is appropriate as the description does not mislead about parameters, and the absence of parameters is handled adequately.

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 with a specific verb ('fetch') and resource ('test-site'), including the URL 'https://test.com' and the transformation action ('convert to markdown format'). It distinguishes from siblings like 'fetch_example_site' by specifying the exact site, but does not explicitly differentiate from 'fetch_website' or 'list_configured_websites' in terms of functionality.

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. It does not mention any context, prerequisites, or exclusions, such as when to choose 'fetch_website' for general fetching or 'list_configured_websites' for listing. Usage is implied only by the tool name and description, with no explicit instructions.

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