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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuinely new behavioral facts: the ID is opaque and stable across token refresh and reconnection, and it differs per user and per organization — useful for caching and identity-matching decisions that annotations cannot convey.

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 identity statement, then the stability caveat, then the scope limitation. Nothing is padded; the only marginal sentence is the final scope disclaimer, which still earns its place by preventing misuse.

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 with a full output schema and complete annotations, the description covers what it returns (organization identity plus a stable opaque profile ID) and what it cannot do. Nothing needed to invoke it correctly is missing.

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 applies and there is no schema semantics to compensate for. The description correctly avoids fabricating parameter talk and instead clarifies that no user/org identifier is accepted.

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 concrete verb ('Identify') and a precisely scoped resource ('the authenticated user's connected organization'), which is unmistakable against the hundreds of get_* siblings that fetch leases, contracts, or accounting records. It stops short of naming a contrasting sibling, but the 'authenticated user' framing already excludes the generic entity lookups.

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?

There is no explicit statement of when to call this versus alternatives such as get_users or describe_operation. The final sentence ('never selects another user or organization') functions as an implicit exclusion, telling the agent not to attempt fetching a different user's profile with it, but the guidance is implied rather than stated.

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