List private profiles

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false, openWorldHint=false). The description adds useful behavioral context beyond annotations: it clarifies the data returned excludes provider IDs, credential values, and paths, and that there is no network access. However, it doesn't describe the return shape or format, and with annotations doing the safety work, this is adequate but not rich.

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?

Very short, but it's a series of comma-separated fragments rather than a structured sentence. It's front-loaded with the scope constraint but reads telegraphically and omits the core action.

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 zero-param list tool with no output schema, the description should at minimum state that it lists local profiles/accounts and roughly what each entry contains. Instead it only describes exclusions, leaving the agent to guess what is actually returned and how it differs from list_provider_accounts.

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?

Zero parameters, so baseline 4 applies. The description adds some semantic value by clarifying what fields are and aren't included in the returned profiles, which is relevant given there are no params to document.

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 title 'List private profiles' and name 'list_accounts' suggest listing accounts, but the description only says 'Local profile labels/default/auth method only' — it never states the action (list) or the resource (accounts/profiles) explicitly. It reads as a fragment of a data-scope disclaimer rather than a purpose statement, making it hard to distinguish from sibling 'list_provider_accounts'.

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 indication of when to use this tool versus 'list_provider_accounts' or any other sibling. There are no alternatives mentioned, no prerequisites, and no context signals to guide selection.

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