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

The annotations already declare readOnlyHint=true, and the description adds meaningful behavioral detail about what the tool returns: public site codes and ready-to-paste script tags. There is no contradiction and no missing safety-critical behavior for a read-only list operation.

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 focused sentence that front-loads the core purpose ('All sites on this account') before adding specific output details. Every word contributes value, and there is no redundancy or filler.

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 parameterless read-only list tool with an output schema present, the description provides sufficient context: scope and key output fields. It could be slightly more explicit about when to prefer this tool over related site-focused tools, but that gap is already covered in the usage dimension.

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?

The tool has zero parameters, so the description does not need to explain parameter meanings. The account-wide scope is stated clearly, and no filtering behavior is implied. This matches the baseline for a parameterless tool.

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 identifies the resource (all sites on the account) and the key output contents (public site codes and ready-to-paste script tags). It lacks an explicit verb like 'Lists' or 'Returns', but the meaning is unmistakable. It does somewhat distinguish itself from sibling tools by emphasizing account-wide scope, though it does not name any alternative.

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 this tool is for retrieving all sites, but it provides no explicit guidance on when to use it versus siblings like get_site_context, get_overview, or portfolio_overview. There are no when-not-to-use conditions or alternative tool references.

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