list_accounts

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

Without annotations, the description carries the burden of disclosing behavior. It does state that returned summaries contain no secrets and explains what the credentials_configured/read_only fields indicate, which is useful. However, it does not explicitly say the operation is read-only or side-effect-free, leaving a gap in safety characterization.

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 two concise sentences, front-loaded with the primary action. It avoids redundancy and every sentence adds value, making it efficient.

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 tool with no output schema, the description covers the main output fields and purpose. However, it omits parameter semantics and provides no usage context relative to sibling tools, making it minimally complete for a tool with these complexities.

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 schema description coverage is 0%, and the description does not mention request_id or idempotency_key at all. Since the schema provides no descriptions for these parameters, the lack of compensation in the description is a significant gap.

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 specific verb and resource: 'Hesapları ... listeler' (lists accounts). It also clarifies the output nature (summaries without secrets) and defines the meaning of fields, distinguishing it from account balance, add, or remove tools.

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 tool versus alternatives. It does not mention that this should be used for listing accounts as opposed to get_account_balance or add_account. The description only states what the tool does, not when it is appropriate relative to other tools.

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