list_accounts

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

Annotations already declare the operation safe (readOnlyHint, idempotentHint, openWorldHint, non-destructive). The description adds no extra behavioral context beyond these annotations, such as pagination behavior, ordering, or whether it returns all accounts by default. It is a minimal statement that doesn't enhance understanding of side effects or limitations.

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 a single, concise sentence that clearly states the action and resource with no redundant or unnecessary information. It is well-structured and direct, maximizing clarity with minimal words.

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 simple list operation with full schema coverage and safety annotations, the description is adequate. However, it lacks any mention of return format, whether pagination is required, or when a search might be more appropriate. Given no output schema exists, some additional context would help, but the tool is straightforward enough that this is a minor gap.

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 fully documents both parameters (limit and offset) with descriptive text, providing 100% coverage. The description doesn't add any parameter semantics beyond what the schema already offers, so the baseline score of 3 is appropriate.

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 uses a clear verb ('Fetch') and resource ('accounts'), making the operation unambiguous. However, it doesn't explicitly differentiate from sibling tools like search_accounts or list_account_groups, though the use of 'list' implies a full collection rather than a filtered search.

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 is provided on when to use this tool versus alternatives such as search_accounts or list_account_groups. The description gives no usage context or exclusions, leaving the agent without direction on tool selection.

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