Who am I

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

Annotations already cover the safety profile (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the description does not need to restate those. It adds the useful context that the tool exposes the currently authenticated identity, but does not describe any further behavior such as response shape or permissions.

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 sentence that front-loads the usage condition immediately. Every word contributes clarii: the action, the target, and a concrete example.

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-parameter, read-only identity tool, the description is complete: it explains when to use it and what it returns conceptually. Annotations supply the safety profile and no output schema is necessary for such a simple operation.

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?

There are zero parameters and schema description coverage is 100%, so no paramter explanation is required. Baseline for no-parameter tools is 4; the description adds no unnecessary paramter noise.

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 uses a specific verb, 'identify,' with a clear resource, the currently authenticated Lizard user. It is immediately distinguishable from all sibling tools, which focus on deployment, billing, secrets, projects, services, and git operations.

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 explicitly states when to use the tool: whenever the agent needs the authenticated Lizard user, with a concrete example ('before asking which workspace or project to act on'). No alternative identity tool exists among siblings, so exclusion/alternative guidance is unnecessary.

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