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

With no annotations, the description carries the full behavioral burden. It does disclose the admin-level gating per operation and that get returns a 'full fiche', which is useful. However, it says nothing about whether set_role is reversible, what list returns, pagination, or side effects of a role change — significant gaps for a mutation-capable admin tool.

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 terse and front-loaded, with each operation on a compact segment and zero filler. The single-word lead 'Accounts.' is efficient as a topic label, though it borders on under-specification rather than being genuinely informative.

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 five-parameter, multi-operation admin tool with no annotations and no output schema, the description covers the op-to-parameter mapping and permission tiers but leaves `_org` unexplained and the return behavior of each op unclear. Adequate but with notable omissions.

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 0%, so the description must compensate, and it partially does: it documents query (email/name/sub), target (email|sub), and role (member|admin|super_admin) per operation. But the `_org` parameter is entirely undocumented in both schema and description, and return shapes are unspecified.

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 names the resource (Accounts) and breaks down three concrete operations (list, get, set_role) with what each does, e.g. 'get (`target` email|sub → full fiche)'. It clearly conveys this is a user-account administration tool, though it does not explicitly differentiate itself from the sibling oto_admin_account or oto_admin_org_member.

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?

It gives per-operation privilege context — 'platform admin' for list/get and 'super admin' for set_role — which tells an agent whether an operation is permissible. It stops short of naming alternatives or stating when not to use it, so it falls just below the top mark.

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