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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds essentially nothing beyond that: it restates the two variants already explained in the schema and appends a legal disclaimer, and it says nothing about payload size (llms-full.txt could be very large) or pagination.

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?

Two short sentences with the core behavior front-loaded and no wasted phrasing. The trailing 'Education only, not financial advice' line is boilerplate but plausibly a required legal notice, so it is only a minor drag on conciseness.

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 simple zero-required-param read tool with no output schema, the description covers the essentials. However it omits any hint about expected output volume or format (especially for the 'full' variant), which is the main thing an agent needs to choose wisely.

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% and the enum parameter is fully documented in the schema, so the baseline is 3. The description's paraphrase ('short' / 'full') adds no format, size, or default information beyond what the schema already provides.

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?

States a specific verb and resource with both variants named (llms.txt map vs llms-full.txt), which distinguishes it from content-listing siblings like list_directory or get_guide. It does not explicitly say how it differs from those siblings, keeping it short of a 5.

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?

No guidance on when to call this instead of get_guide, get_disclaimer, list_directory, or search_content. The only 'when' signal is the variant toggle, which is already documented in the schema, and the 'Education only' line is a legal disclaimer rather than usage direction.

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