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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description doesn't need to repeat safety. It adds useful behavioral detail: the sort order (newest-first) and the list of returned fields, which helps an agent understand the output. It does not contradict annotations, and it adds value beyond them, but it doesn't disclose potential pagination or limits. Given the annotations cover safety, a 4 is appropriate.

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, front-loaded sentence that states the action, the resource, the ordering, and the returned fields without any fluff. Every word contributes.

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 simple read-only list tool with two well-documented parameters and no output schema, the description provides all necessary information: what it lists, the ordering, and the fields returned. It does not need to explain return format since there is no output schema. The only minor gap is the lack of mention of pagination, but that is not critical for a version list. Overall it is complete.

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?

Both parameters are fully described in the schema (100% coverage), including the meaning of site_id and workspace_id. The description adds no additional parameter-specific semantics beyond what the schema provides, so the baseline 3 applies.

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 lists a site's published versions, specifying the sort order (newest-first) and the exact fields returned (content hash, content kind, entry path, size, file count, timestamp). This is a specific verb+resource, and while there are many list tools among siblings, 'versions' is a distinct resource, so it is unambiguous.

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 usage when you need to inspect a site's published versions, but it does not explicitly mention when not to use it or point to alternatives. However, since no sibling tool lists versions, the context is clear enough, but the lack of explicit alternatives or exclusions keeps it at a 3.

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