Identify user

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavioral context not in the annotations: the required OAuth scope (identify:read) and that an OAuth access token is mandatory while API-key identity is out of scope. It still omits what data is returned or any rate/consistency behavior.

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?

Four short sentences, front-loaded with the action ("Identify user. Reads account data.") before the auth constraints. It is tight and wastes little, though the opening echoes the title.

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 simple, single-optional-param read tool with no output schema, the auth requirements are the key missing context and they are supplied. The gap is the lack of sibling disambiguation, leaving an agent unsure when to prefer this over other identity-related endpoints.

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?

With a single parameter at 100% schema description coverage, the schema already fully documents the optional "account" field and its default resolution. The description adds no parameter-level meaning, so the baseline of 3 is appropriate.

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?

"Identify user. Reads account data." states a verb and resource, but "Identify user" largely restates the title and the description never distinguishes this from close siblings such as workspaces_identify or workspaces_permissions. An agent cannot tell from the text alone which of these identity/account endpoints to pick.

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 useful conditional context ("OAuth integrations require identify:read", "API key identity is not this endpoint"), which implies when the tool applies. However, it offers no explicit guidance on when to use this versus alternative sibling endpoints, so usage remains partially inferred.

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