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

readOnlyHint already tells the agent this is a safe read, but the description adds genuinely new information: the response is markdown and corresponds to the site's llms.txt, which is meaningful given there is no output schema. It does not mention response size or whether the full page index can be large, which is the main remaining behavioral unknown.

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?

A single front-loaded sentence with the scope enumerated up front and the return format placed at the end where it belongs. No filler, no repetition of the tool name.

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 zero-argument, read-only tool with no output schema, the description covers what comes back and in what format, which is the essential gap. It could go one step further by noting the response can be large or that it is the recommended first call, but nothing needed to invoke it correctly is missing.

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 takes zero parameters, so per the rubric the baseline is 4. There is nothing about arguments that the description could or should explain.

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 names the exact payload: site orientation plus an index of every page, explicitly framed as the site's llms.txt in markdown. That distinguishes it from list_posts/read_post/search_posts, which all operate on individual posts. It stops short of a crisp verb ('get site overview'), opening with a noun label instead.

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 phrase 'when to use it' describes the *content of the document* (the site's own guidance), not guidance for the calling agent. Usage as an entry-point/orientation call is only implied by the word 'Orientation'; there is no explicit 'call this first' or 'use instead of X' statement.

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