Url Rag Chunks

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

Disclosures beyond annotations: confirms no JavaScript execution, no access control bypass, deterministic bounded chunks, and caching behavior. No contradiction with readOnlyHint, idempotentHint, or destructiveHint.

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?

Three sentences, no waste. First sentence states purpose, second adds constraints, third explains parameter usage. Front-loaded and efficient.

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?

Covers purpose, constraints, parameter usage. Output schema exists, so return values documented elsewhere. Complete for a simple tool with good annotations.

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 coverage is 100%, but description adds value by reinforcing 'absolute public URL' for url and explaining caching rationale for fresh. Baseline 3, plus extra context.

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?

Description clearly states the tool splits readable text into deterministic bounded RAG chunks, specifying the verb and resource. It is distinct from sibling URL tools by focusing on RAG chunking.

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?

Provides clear context: use only for public HTTP(S) resources, and explains when to set fresh=true/false. Does not explicitly contrast with siblings but adequate for usage.

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