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

Annotations already declare readOnly/idempotent/non-destructive, yet the description still adds real behavior: a 30,000-character cap per call, part-wise reads via the returned nextOffset, and that binaries yield only size and sha256. It stops short of stating error behavior when the sha256 does not match, which is the one unexplained branch.

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?

Three dense sentences, front-loaded with the action and return contract; the text-versus-binary split and the pagination rule each earn their line. No filler and no restatement of the title.

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?

There is no output schema, and the description compensates fully by describing what comes back for text files, the nextOffset continuation token for long files, and the size/sha256-only shape for binaries. An agent has enough to call this and interpret the response without guessing.

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 67% and siteId is undocumented, but the description explains the offset/pagination relationship (feed the returned nextOffset back as offset) and the 30k cap that triggers it, which goes beyond the schema's bare "Character to start from". path and siteId get no added meaning beyond the schema.

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 ("Returns the current content of one file on a RunLite site's live version") with scope qualifiers that separate it from get_site, upload_files and deploy_site. The sha256-verification detail further pins down exactly what is being read.

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?

Usage is implied by the "live version" scoping and the closing "Changes nothing", but no sibling is named and there is no explicit when-to-use/when-not guidance. An agent can infer this is the read path versus upload/deploy tools, but must do the routing itself.

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