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

With no annotations, the description carries the burden of disclosure. It makes the read-only nature clear via 'Check' and specifies exactly what is inspected: robots.txt directives for a named set of AI crawlers and the presence of llms.txt. It does not discuss rate limits or errors, but nothing about the behavior is hidden or misleading.

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 two sentences with no filler: the first front-loads what is checked, and the second explains who benefits. The crawler-name list is long but earned, because it removes ambiguity about which bots are in scope.

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 one-parameter, low-complexity tool, the description covers the target resource, the exact crawlers of interest, and llms.txt; the schema covers the input contract. It could mention the response shape or behavior when robots.txt is absent, but those are minor gaps for a check-style tool with no output schema.

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 single parameter is already fully described in the schema with coverage at 100%, including the fact that any URL on the site works and the origin is derived. The description reinforces this by talking about 'a site's robots.txt', but it adds no new parameter semantics beyond what the schema provides, so it stays at the baseline.

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 opens with a specific verb and resource: 'Check a site's robots.txt for explicit directives targeting known AI crawlers', then adds llms.txt as a second target. It also enumerates the exact crawler names and differentiates itself from generic siblings like check_robots_sitemap by scoping to AI crawler policy.

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 gives clear, concrete use cases: publishers checking whether their AI-crawler content policy matches intent, and auditing a competitor's stance. It does not explicitly mention alternatives or say when not to use this tool, so it misses the highest bar for routing an agent away from siblings like check_robots_sitemap.

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