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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered, and the description adds genuinely useful extra behavior: the ownership restriction that rejects sites whose stats are merely public, and the point that settings are changed elsewhere ('settings links to where each is changed'). It also discloses the shape of the returned settings since no output schema exists.

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?

It is one run-on archaic sentence with no structure, burying the key precondition and the refusal rule inside a long enumeration of return fields. Every fact is relevant, but the phrasing and lack of front-loading make it hard for an agent to parse quickly.

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 compensates by enumerating the returned settings (tag, tag_docs, time zone, group, public, email_reports, excluded, search_rules) and explains the ownership restriction. Combined with annotations and the fully documented single parameter, an agent has enough to call it 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% and there is only one parameter, domain, whose schema description already says 'A domain from list_sites.' The description's 'Name the site by its domain' adds no meaning beyond that, so this is the baseline case.

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 resource and verb: it returns how one of the user's own sites is configured. It also names siblings (list_sites for the group value, check_install to verify the tag) and explicitly contrasts itself with the read-only public-stats case.

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?

It gives a clear precondition ('Name the site by its domain') and a when-not rule ('a site read only because its stats are public is refused, as its settings are its holders' alone'), plus a follow-up routing to check_install once the tag is installed. No explicit exclusions against the other analytics siblings, but usage context is well covered.

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