list_user_accounts

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds no behavioral context beyond the raw endpoint path: no mention of pagination defaults, result size, ordering behavior, or what an "account" represents.

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 the same phrase is printed twice, so the single useful sentence is duplicated rather than front-loaded with new information. Brevity here reflects under-specification rather than discipline.

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 six parameters, no output schema, and a filterable/paginated list endpoint, the description leaves the agent without any sense of what comes back or how the filters interact. An agent can call it, but only by reading the schema from scratch.

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 description coverage is 100%, so the six parameters (page, size, email, default, orderBy, x-trace-id) are fully documented in the schema. The description contributes nothing about the filtering or paging capability, which is acceptable only because the schema carries that burden.

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?

"List of your accounts" states a resource and implies a read, but it is essentially a restatement of the tool name `list_user_accounts` with no additional specificity. The appended endpoint path adds nothing an agent could not infer from name plus annotations.

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 guidance on when to use this versus alternatives. The possessive "your" weakly implies accounts scoped to the calling user (as opposed to `retrieve_user_list`), but this is inference, not instruction, and related tools like `switch_account` and `make_default_account` are never referenced.

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