List configured accounts

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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is low, yet the description adds real value by enumerating what is NOT returned (no secrets, file paths, provider identity, or network). This privacy/scope disclosure goes beyond the structured fields.

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?

A single compact sentence, front-loaded with what the tool returns and followed by its exclusions. It is terse but each clause carries content; the telegraphic style borders on fragmentary but stays within reasonable conciseness.

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 zero parameters and no output schema, the description must carry the return-value burden, and it does describe the returned fields (labels, default flag, credential availability) and the notable omissions. Format details are not given, but for a trivial no-arg list tool this is largely 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 (empty object schema), so there is nothing to document and the baseline of 4 applies. The description correctly implies a no-argument listing call.

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 reads as a content/scope specification ('Local profile labels/default and credential availability only') rather than a clear verb+resource statement; the verb 'list' only appears in the name and title. An agent can infer it enumerates locally configured account profiles, but the purpose is implied rather than stated.

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?

No when-to-use guidance is provided; the text is purely a scope disclaimer about returned fields. There is no mention of prerequisites, conditions, or how this relates to other listing tools.

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