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

Annotations already declare read-only, idempotent and non-destructive, so the bar is lower; the description still adds the return encoding (utf8 or base64), token/auth semantics, and the cost signal 'Does not charge.' It stops short of error behavior or size limits.

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?

Front-loaded with the return type, then parameters, then auth, then safety/cost. Sentences are short and mostly earn their place; the parenthetical '(needs account token)' is a touch abrupt but not wasteful.

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?

With no output schema, the description correctly covers the return format (text or base64) plus auth requirements and cost, which is what an agent needs before calling. Missing only failure modes such as a nonexistent path or binary handling.

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%, so both parameters are already documented; the description's 'site is the address' and 'path is the file' merely restate them, adding only the token note. Baseline 3 applies when the schema does the heavy lifting.

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 one file from a site you can update, as utf8 text or base64.' The singular 'one file' implicitly separates it from list_site_files, and the token note hints at edit_site_file, but no sibling is named explicitly.

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?

Gives clear prerequisites: an account token is needed, a site token works (including before the site is claimed), and 'Without a token, claim the site first.' It does not explicitly contrast with list_site_files or edit_site_file, so the when-to-choose gap keeps it off a 5.

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