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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds real behavioral context the annotations cannot: what is returned for text vs binary assets, that history surfaces the last 20 versions for restore_version, and that full reads may be size-limited ("if the site isn't too large"). The trailing Ginta UI .zip note is tangential but harmless.

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 usage trigger and return description in two tight sentences. The parenthetical about downloading a .zip from the Ginta website menu is extraneous to the tool's behavior and slightly dilutes focus.

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?

Output schema exists, so return values need not be spelled out, yet the description still summarizes them helpfully. Combined with 100% schema coverage and non-destructive annotations, an agent has everything needed to invoke this correctly.

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 100%, so the baseline is 3, but the description adds meaning beyond the schema by linking history:true to restore_version and clarifying that paths restricts the read to a subset of files. It doesn't add format or edge-case detail for paths beyond the schema's own limits.

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 a site's files and, with history, its saved versions) and details the return shape: text contents inline, images/fonts as a list of addresses. It is clearly distinguishable from siblings like restore_version, preview_site, and list_sites.

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 an explicit when-to-use trigger ("Use before editing an existing site, or when the owner wants their code") and ties the history parameter to its downstream consumer, restore_version. It also tells the agent how to narrow scope with paths.

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