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

Annotations already establish readOnly, idempotent, non-destructive, closed-world behavior, so the description only needs to add context. It does add useful behavioral context: the identity returned is the OAuth-authorized human, it includes role and teams, and connection scopes or identity restrictions may shrink the toolset. It omits what happens when the token has no associated human principal.

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?

Three short sentences, front-loaded with the return content. The final sentence about connection scopes limiting available tools is slightly tangential to calling this specific tool, but it is not padded or repetitive.

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 and no parameters, the description carries the burden of describing the return value, and it does so (principal, workspace role, teams). A brief note on error behavior when no user identity is available would make it complete.

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 the baseline is 4; there is no parameter semantics to explain. The description correctly implies a single implicit subject (the authenticated user) rather than any filter arguments.

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 gives a specific verb and resource: it returns the Human Principal behind the OAuth connection, plus their workspace role and teams. That is clearly distinct from the sibling list_users/list_members, which enumerate many users, but the differentiation is implied rather than naming a sibling outright.

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 implied by the sentence 'me and my issues refer to this user', which tells the agent this tool resolves the pronoun used by list_my_issues. There is no explicit when-to-use/when-not guidance, and the scope caveat is about tool availability rather than about choosing this tool.

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