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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real value beyond them by listing the returned fields (id, name, sharing, timezone, created_at) and the underlying GET endpoint, which matters because there is no output schema. It still omits auth requirements and error behavior.

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?

Two short, front-loaded fragments with zero filler: the resource and its returned shape come first, then the endpoint. Nothing is padded or repeated from the title or schema.

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 single-parameter read with no output schema, the description supplies the return field set, including the sharing enum, which is the main thing an agent would otherwise lack. It stops short of documenting the response structure precisely or noting auth/failure modes.

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% and the schema already explains the site_id format, the tracking-code correspondence, and points to fathom_list_sites as a discovery path. The description adds nothing about the parameter, so the baseline of 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?

Names a specific retrieval ("One site") and enumerates the fields it returns, which is more than a restatement of the title. It implies single-site scope versus the sibling fathom_list_sites, but never names that sibling to draw the contrast 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?

The phrase "One site" implies the usage condition (fetch exactly one known site by id), which is enough to distinguish it in practice from fathom_list_sites. However there is no explicit when-to-use/when-not guidance, no prerequisites, and no naming of alternatives such as fathom_update_site or fathom_list_sites.

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