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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the source ('direct fetch') and pricing ($0.005 per call), which are useful behavioral context beyond the annotations. It does not mention parsing behavior details or edge cases, but the annotation coverage raises the baseline.

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 sentences plus a compact source/cost/method suffix. Every part earns its place: the title explains what's fetched, the description adds parsing behavior, and the suffix provides source, pricing, and HTTP method without bloat.

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 single-parameter, read-only, idempotent tool with full schema coverage and helpful annotations, the description is nearly complete. It lacks explicit mention of return format or failure behavior, but no output schema is expected and the annotations cover the operation's safety profile. A 4 reflects the minor gap in response semantics.

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 description coverage is 100%, with the url parameter clearly described as 'Any URL on the target site' and a helpful example. The description adds the overall purpose but no additional parameter-level semantics, so the baseline 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 states a specific verb ('Fetch and parse') and resource ('a site's robots.txt and llms.txt'), clearly distinguishing it from the data-lookup siblings. It doesn't explicitly contrast with a similar tool, but the resource is specific enough that an agent can understand what it does.

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 implies usage by noting it fetches and parses robots.txt/llms.txt and takes any site URL, but it gives no explicit guidance on when to prefer this over alternatives or when not to use it. For a niche tool among many data-lookup tools, this minimal context is adequate but not enriched.

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