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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description's only added behavioral fact is the returned field set (id and email), which is also covered by the output schema, so it adds little genuinely new context.

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 eight-word sentence that front-loads the verb and resource with zero filler. Nothing is repeated from the title beyond what is necessary, and nothing could be trimmed without losing information.

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 zero-argument identity getter with rich annotations and an output schema, the description covers what the tool returns and whose account it targets. The one missing element is the authentication precondition (behavior when no account is connected), which matters for a tool whose entire semantics depend on a connected session.

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 and the schema is an empty object, so there is no parameter meaning to explain. Baseline 4 applies; the description correctly avoids inventing argument semantics.

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 a specific verb and resource ("Get the connected account's id and email") and states exactly which fields come back. The word "connected" implicitly scopes it to the authenticated account, which loosely separates it from the get_public_profile sibling, though it never names that alternative explicitly.

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?

Usage is only implied: an agent can infer this is the call for the current user's own identity data, and "connected account" hints at the authenticated context. There is no explicit when-to-use, no when-not-to-use, and no routing advice versus get_public_profile, which is the sibling most likely to be confused with it.

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