Site Llms Txt

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

Discloses key behaviors: no JavaScript execution, no access control bypass, and cache reuse via the 'fresh' parameter. Annotations already indicate read-only and idempotent, but the description adds valuable context about caching and security constraints, exceeding what annotations provide.

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 three sentences, each serving a distinct purpose: stating the core function, specifying constraints, and providing parameter usage advice. It is front-loaded with the main action and contains no superfluous words.

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 simplicity (2 parameters, boolean fresh, output schema exists), the description covers all necessary aspects: what it returns, when to use it, parameter semantics, and behavioral constraints. The presence of an output schema removes the need to detail return values.

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% with descriptions for both parameters. The tool description adds practical guidance on how to use the parameters, such as 'Pass url as an absolute public HTTP(S) URL' and when to set 'fresh=true', which adds value beyond the schema alone.

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 returns 'bounded llms.txt text when publicly available,' which is a specific verb-resource pair. It distinguishes itself from sibling tools like url_text or site_robots by targeting a specific file format (llms.txt).

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?

Explicitly states when to use ('public HTTP(S) resources'), what it does not do ('does not execute JavaScript or bypass access controls'), and provides clear guidance on the 'fresh' parameter (when to set true/false). This helps the agent decide between this tool and alternatives.

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