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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description still adds real context beyond them: device tokens are shortened (redaction), and approvals are limited to the last 90 days (scope/time window). It does not mention rate limits, payload size caps for users with many pushes, or any auth/compliance framing for what is effectively a PII export.

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?

One sentence, front-loaded with the core action and output format, then the contents list. No preamble, no repetition of the title, and every clause carries information the schema and annotations do not.

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?

No output schema exists, so the description deliberately compensates by enumerating returned fields and format ('as JSON'), and it discloses the 90-day approvals window and token shortening. What is still missing is behavior for large users (pagination, truncation, size limits) — meaningful for a bulk export tool but not fatal.

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% with a single required user_id already documented as 'Your own id for the user.' The description reinforces the single-user scope ('one user id') but adds no format, source, or validation semantics, so the schema continues to do the heavy lifting.

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?

Names a specific verb and resource ('export ... one user id as JSON') and enumerates exactly what is bundled: devices, topics, passkeys, authenticator status, approvals, consent history, pushes. That enumeration implicitly distinguishes it from the granular list_devices / list_passkeys / list_pushes siblings, but it never names an alternative explicitly, so the differentiation is inferred rather than stated.

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?

There is no explicit 'use this when' or 'use X instead' clause; the agent must infer that this is the single-call aggregate for a full user profile versus the many narrow list_* / get_* siblings. The 'Everything SignOps holds' phrasing implies the bulk-export use case, but nothing is stated about alternatives or exclusions.

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