list_accounts

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds none of the behavioral context such as pagination, authentication, or what is actually returned. It merely restates the action, so it does not exceed the annotations in any meaningful way.

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 extremely tight: a single verb phrase and the HTTP endpoint. Both earn their place. There is no filler, fluff, or redundant explanation. It front-loads the purpose immediately.

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?

This is a simple, zero-parameter, read-only with an output schema and annotations, so it does not need to explain parameters or return value details. However, it lacks any description of what 'system accounts' actually are or when to use this over the many list tools, so an agent could still be misled.

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 input schema has zero parameters, so there is no parameter meaning to add. The baseline for a zero-parameter tool is 4, and the description is not required to elaborate further. Nothing from the description conflicts with the empty schema.

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 states a specific action ('Get') on a specific resource ('System Accounts') and even gives the endpoint. It is not a tautology, and it is distinct enough to know it retrieves accounts, but it does not differentiate from sibling tools like list_users or list_servers, so it misses the full context.

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 gives no guidance about when to use this tool versus alternatives. There is no mention of whether system accounts are the same as user accounts, no prerequisites, and no pointer to other tools. An agent is left to infer the use case from the name and the one-liner.

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