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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered externally. The description adds only the returned field set, with no note on permissions, freshness, or what 'notification choices' actually contains; useful but thin, hence a 3 rather than higher.

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?

A single short sentence with zero filler, front-loading the most identifying information (account id, display name). Nothing is padded or redundant.

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?

With no output schema, the description's enumeration of returned fields is doing real work and is the right move. However, it doesn't resolve ambiguity against the many sibling readers (whoami, profile_get, contact details via contacts_mine), so an agent still lacks enough to route confidently in this large toolset.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. Schema coverage is 100% and the empty object schema matches the description's implication of an argument-free call.

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 enumerates what the tool returns (account id, display name, email, notification choices), which tells an agent the resource is the caller's own account. But it is a bare noun phrase with no verb, and it does not distinguish this from close siblings like whoami, profile_get, or identity_tree, leaving the agent to guess which read 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?

There is no statement of when to use this versus account_update (the write counterpart) or the other identity/account readers in the sibling list. The only implicit signal is the word 'Your', which hints at the self-scoped read, but no explicit context or exclusion is given.

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