tokportal_list_accounts

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

The description adds no behavioral context beyond the annotations (readOnlyHint, idempotentHint, destructiveHint). It does not explain what 'delivered' means, how pagination works, or what the response looks like. For a list tool with no output schema, some behavioral disclosure would be valuable.

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 sentence with no wasted words. It is concise and front-loaded. However, it is almost too brief and could benefit from a bit more structure or context without losing conciseness.

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?

Given the tool has 5 parameters, no output schema, and no behavioral annotations, the description should provide more context about what 'delivered accounts' means, the expected response format, and any constraints. The current description is incomplete for an agent to fully understand the tool's behavior.

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% and each parameter has a description (e.g., page, banned, country, per_page, platform). The description adds no additional meaning beyond what the schema already provides. Baseline 3 is appropriate as the schema carries the burden adequately.

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 'List delivered accounts.' clearly states the action (list) and the resource (delivered accounts). It is specific enough to convey the core function, but it does not differentiate this tool from siblings like tokportal_get_account or tokportal_list_account_bans, which could cause confusion about which tool to use.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites, exclusions, or context for when 'delivered accounts' is the appropriate scope. With many sibling tools, this omission makes it harder for an agent to select the correct tool.

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