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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so 'Read-only, no arguments' largely restates structured data. The one genuinely additive trait is the semantic caveat that the agent's bot user is 'never assignable' and that the member is used for spend + audit attribution, which tells the agent how to interpret the values. Beyond that there is no disclosure of failure modes (e.g. what happens with an unauthenticated/expired key) even though the tool is the first call in a session.

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?

Two sentences, both load-bearing, with purpose and return contents front-loaded and the usage rule second. The field enumeration is a long comma-run and slightly dense, but each item conveys distinct returned information.

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, the description must convey what comes back, and it does so field-by-field plus the important 'never assignable' constraint on the bot user. For a zero-param read tool this is complete enough that an agent can call it without guessing.

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?

Zero-parameter tool, so the baseline is 4; the description confirms 'no arguments', matching the empty schema with additionalProperties=false. No further parameter detail is possible.

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?

Names a specific verb+resource ('who am I') and then enumerates exactly what identity facts are returned: workspace, acting member, bot user, key provider/scope/projects, synthesised role. Nothing among the ~120 siblings does this, and the tool is distinguishable on the name plus the returned-field list alone.

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?

'Other tools' output does not state this identity, so it is the reliable first call in a cold start' gives an explicit selection rule and a concrete trigger (cold start) that no sibling provides. It also implicitly excludes itself from the mutation workflows that dominate the sibling list.

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