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

Annotations already declare the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description only needs to add context beyond that. It contributes the word 'allowlisted' (only the three enum names are reachable) and distinguishes 'physical ... file' from 'observed public output', but says nothing about fetch behavior, missing-file handling, or error outcomes for an openWorld read.

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 compressed sentence with the resource and the read-before-write rule front-loaded; nothing is redundant. It is terse to the point of feeling abbreviated ('observed public output' is unexplained), which is the only thing keeping it off a 5.

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 two-required-parameter, no-output-schema tool the definition covers the essentials of identity and scope. What it leaves out is what 'observed public output' actually means and how a missing or unreadable file is reported, which an agent needs in order to interpret a result.

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 50% and the covered half is the one that matters: site_id tells the agent to call list_sites first and forbids URLs or post IDs, and name is a closed enum of three literals. The description adds nothing about either parameter, which is defensible here because the remaining documentation gap is a self-describing filename enum.

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 ('Inspect') and a tightly scoped resource: one allowlisted physical public text file plus its observed public output. The enum of robots.txt/llms.txt/llms-full.txt makes the scope concrete, and 'read before writing' hints at its pairing with wp_write_public_file without naming it, so sibling differentiation is implied rather than explicit.

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 'read before writing' gives one real sequencing guideline and implies wp_write_public_file is the mutation counterpart. However, there is no explicit when-not guidance, no statement about what to do if a file does not exist, and no mention of alternatives such as wp_read_post for content that is not an allowlisted public file.

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