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

Annotations already establish read-only, idempotent, closed-world, non-destructive behavior, so the bar is lower. The description adds a genuine behavioral fact beyond annotations: the tool is available to every role regardless of privilege.

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?

Front-loaded with the return contents, followed by the actionable 'Call it first' and the access note. Slightly flowery phrasing ('Who you act for', 'the level they reach it at') but no wasted sentences.

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 present, the description carries the load of describing return values and does so by enumerating identity fields and reachable projects. No parameters and no annotations gaps leave little else to cover, though the notion of project 'level' could be more precise.

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 per the baseline this scores 4. There is nothing for the description to disambiguate regarding inputs.

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 specifies what comes back (name, email, platform role, organization, and reachable projects with access level), so an agent understands this returns the current signed-in identity rather than org-wide or member data. It never states the verb 'get/return' explicitly, framing it as 'Who you act for,' but the content list is specific enough to separate it from get_organization and list_members.

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?

'Call it first' is an explicit sequencing directive, and 'Every role holds it' tells the agent that no permission gating applies. There is no named alternative or when-not condition, but the primary usage context is clearly stated.

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