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

With no annotations, the description carries the full burden, and it does substantial work by disclosing the exact response payload, including the nested fact that connected data sources are returned with their last sync times (useful for judging freshness). It also implies a non-mutating lookup via 'Get'. It stops short of stating error behavior for an unknown site_id or any permission requirements, which are the only notable gaps.

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 sentences, fully front-loaded: the returned fields come first and the My_Sites shape reference is a compact second sentence that earns its place by anchoring the response format. No filler, no restating of the name or title.

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 and no annotations, the description must convey the return contents, and it does so field by field, including the nested data-source sync times. The shape reference to My_Sites rounds it out, though the agent must already know that sibling's output to fully reconstruct the response, and invalid-ID behavior is unaddressed.

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 single site_id parameter is already documented in the schema, so the baseline of 3 applies. The description adds only indirect context (that the ID selects one site whose details are returned) and no syntax, format, or lookup semantics beyond what the schema provides.

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 states a specific verb ('Get') and resource ('one site') and enumerates exactly what is retrieved: name, domain, public URL, default language, added date, and connected data sources with last sync times. It also explicitly relates itself to the sibling My_Sites ('Same shape as a row from My_Sites'), so an agent can distinguish the single-site lookup from the all-sites list without opening either schema.

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?

Usage is implied rather than stated: the phrasing 'one site's' plus the reference to My_Sites makes it clear this is the single-record counterpart to the list tool, and the required site_id confirms the selection context. However, it never says when to prefer this over My_Sites, or what to do when only one site is known, so the guidance is inferable but not explicit.

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