Get current identity

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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is known. The description adds non-obvious behavioral context by disclosing that it returns basic server info and a derived `assignedToValue`, which an agent could not infer from the tool's name or annotations alone.

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?

The description is two sentences with no filler. It front-loads the primary purpose, then lists the returned fields and the practical `assignedToValue` use case, making every sentence informative.

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 tool with no output schema, the description provides a complete picture: it names the identity attributes, the derived assignment value, and the server info fields. An agent can confidently call this tool and know exactly what to expect.

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 has zero parameters and the empty input schema is fully covered, so there are no parameter semantics to clarify. The description correctly focuses on what is returned instead, which is the relevant semantic information for an agent.

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 ('Identify') and a specific resource ('the user behind the configured PAT'), and enumerates what is returned: id, display name, account, descriptor, assignedToValue, and server info. This clearly distinguishes it from sibling tools like search_identities, which searches, rather than returns the configured identity.

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?

The description gives a clear usage context: it identifies the PAT's user and specifically calls out the `assignedToValue` for update_work_item(s), signaling when this tool is useful. It does not explicitly mention alternatives or when not to use it, but the provided integration hint is strong enough guidance for the main use case.

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