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

Annotations declare readOnlyHint=true, and the description aligns with this by describing a non-destructive test action. The description does not add extra behavioral context such as edge-case handling, return format, or the need to provide the full robots.txt content as a string, which would be valuable beyond the annotation.

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 a single, concise sentence that immediately conveys the tool's core purpose. It has no unnecessary filler and is well front-loaded with the action 'Test'.

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?

The tool is simple and read-only. The description clearly states what it does, but since there is no output schema, it leaves the return value ambiguous (e.g., a boolean vs. detailed report). However, the phrase 'whether ... allows or blocks' strongly implies a boolean result, making it mostly complete for a straightforward tester.

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 schema provides no parameter descriptions (coverage 0%), so the description must clarify the parameters. It explicitly names all three: 'robots.txt' (robotsTxt), 'URL path' (url), and 'user-agent' (userAgent). This gives meaningful semantics, although it does not detail the exact format of the robotsTxt parameter (e.g., whether it is the file content or a URL).

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 'tests whether a robots.txt allows or blocks a given URL path for a given user-agent.' This specifies a concrete action (test), the resource (robots.txt), and the relevant inputs (URL path, user-agent). It distinguishes itself from sibling tools like robots-txt-generator by focusing on testing rather than generation.

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 the tool is for checking robots.txt conformance, but provides no explicit when-to-use guidance or comparison with alternatives. Sibling tools such as robots-txt-generator are not mentioned, so the user must infer the intended use case from the name and description.

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