web_preflight

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

The description explains the return values (estimated tokens, content type, safety check) and the rationale (avoid context flooding). It lacks details on side effects like network activity, but is otherwise transparent.

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 two sentences long, each sentence serving a clear purpose. No wasted words, making it 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 lack of annotations and output schema, the description covers the essential aspects: purpose, returns, and usage guidance. It is complete enough for a simple preflight check tool.

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 input schema already fully describes the parameters (url and timeout). The tool description does not add parameter-specific semantics beyond the schema, so a baseline score of 3 is appropriate.

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 as checking page size and metadata before fetching, with a specific verb ('Check') and resource ('page size and metadata'). It distinguishes from sibling fetch tools by positioning itself as a preliminary step.

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 explicitly advises 'Always call this first to avoid context flooding,' providing clear when-to-use guidance. It could mention when not to use it, but the context with fetch tools makes it distinct.

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