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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered without the description. The description adds no behavioral context beyond that — no permissions, error conditions, or visibility scoping rules — its content is entirely return-field enumeration.

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 purpose is front-loaded in the first clause, which is good, but everything after it is a single sprawling sentence packing a dozen returned fields with parenthetical asides. It would read far better as a short purpose line plus a structured list of returned fields.

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 carries the full burden of telling the agent what comes back, and it does so thoroughly — field names, types (ISO or null), and derived values like link_status are all disclosed. It falls short only on error/permission behavior and on not distinguishing itself from get_site_content.

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 site_id and workspace_id are already documented, including the multi-workspace write rule and personal-space default. The description adds no parameter-level meaning beyond the schema, making the baseline 3 correct.

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 opening verb+resource is unambiguous ("Get a single site's status, visibility, current version metadata..."), which cleanly separates it from list_sites and from content-oriented siblings like get_site_content. It never names a sibling explicitly, so an agent must infer the boundary rather than being told it, which keeps this short of a 5.

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?

There is no when-to-use, when-not-to-use, or alternative-naming guidance anywhere in the text. The schema hints at list_workspaces for the workspace_id value, but the description itself offers no routing help between get_site, get_site_content, and list_sites.

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