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

With no annotations, the description carries the full behavioral burden and discloses the critical authorization requirement ('Platform staff only (account session)'). However, it says nothing about pagination behavior despite limit/offset parameters, return ordering, or rate limits, leaving gaps for a list tool returning potentially many records.

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?

Two compact sentences, each front-loaded with the most important information: the access constraint first, then the returned data and search capability. No filler or redundancy.

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 4-parameter list tool with no output schema and no annotations, the description covers the authorization requirement and the returned field set well, but omits pagination semantics and the fact that results may be large given no required parameters. It's adequate but leaves meaningful gaps.

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 description coverage is 0%, so the parameters are undocumented in the schema itself. The description partially compensates by explaining that filtering works by email or name (mapping to the 'query' parameter) and mentions suspension status (mapping to 'status'), but does not address 'limit' or 'offset'.

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 verb (list) and resource (platform accounts), then enumerates the returned fields (email, name, created time, workspaces, platform role, suspension). This clearly distinguishes it from siblings like platform_accounts_get, platform_accounts_suspend, and members_list.

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 explicitly states the access condition 'Platform staff only (account session)' and clarifies the search behavior ('Search by email or name'), which provides clear context for when this tool applies. It doesn't name an alternative like platform_accounts_get for single-account retrieval, so it falls short of a 5.

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