list_account_tokens

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

No annotations are provided, so the description carries full responsibility for exposing behavioral traits. It implies a read-only listing operation, but discloses no auth requirements, pagination behavior, ordering, filtering, or response shape.

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?

Single sentence, front-loaded verb and resource, zero filler. The description is appropriately sized for a simple one-parameter list operation.

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?

Basic calling intent is clear and the one parameter is documented, but with no output schema and no annotations, the description omits usage context such as pagination or how these API tokens differ from access service tokens. It is minimally viable but leaves room for ambiguity.

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 coverage is 100% because the only parameter, account_id, already has its own description. The tool description adds no additional meaning beyond the schema, so the baseline 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?

Clear verb ('List') and resource ('API tokens') with account scope, so an agent can grasp what the tool does. It distinguishes from the singular sibling get_account_token, but it does not explicitly differentiate from list_access_service_tokens, which could be confused.

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 instead of related siblings such as list_access_service_tokens or get_account_token. There are no exclusions, prerequisites, or alternative-selection hints; the description simply states the operation.

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