List configured sites

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

Annotations already cover the safety profile (readOnly/openWorld false/idempotent), but the description adds meaningful context beyond them: output is local profile data only and explicitly excludes site URL, username, password path, and provider identity, i.e. it will not leak credentials. The 'no network request' claim reinforces rather than contradicts openWorldHint=false.

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 short and front-loads the positive scope clause before the exclusions, which is good. However, it is a semicolon-joined fragment with no main verb, so the brevity comes at the cost of readability rather than being crisp prose.

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 0-parameter, read-only tool this is nearly adequate; with no output schema the description is the only place to explain the return payload, and it does sketch the fields (labels, default, credential source). It still leaves the account-vs-site ambiguity and the shape/count of results unresolved, so it falls short of complete.

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 takes zero parameters, so the baseline is 4. The description correctly offers no parameter detail, and there is nothing for it to compensate for.

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 is a verbless fragment that names return-scope items ('Local profile labels/default/credential source only') but never says what the tool does. The name (list_accounts) and title (List configured sites) disagree on the resource, so the agent gets mixed signals about whether it is listing accounts or sites.

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 explicit when-to-use, no prerequisites, and no named alternative sibling. The only indirect guidance is the negative-clause style ('no ... network request'), which hints this is the local-only variant versus tools that make network calls, but that is inference rather than stated guidance.

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