identity_get_user_in_any_organization

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

Annotations already cover safety (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=true), so the description's marginal value is deprecation status and the role-access matrix — both genuinely non-obvious. It omits return shape and any note on whether the deprecated endpoint is still served. The markdown table is also rendered as raw HTML entities, reducing readability.

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-loading '[DEPRECATED]' is the right call and the follow-on mitigation pointer is immediate. But the four-row access table with escaped check/cross entities and a bare GET path consumes most of the text for modest informational gain.

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 should say what a returned user record contains, and it doesn't. For a deprecated two-parameter read tool, deprecation and role gating are adequately covered, but expandProfile semantics and response content are 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?

Schema coverage is only 50%: userId's schema description is just '(path)' and expandProfile has no description at all. The description restates 'by user ID' and shows the {userId} path placeholder, but adds nothing about what expandProfile does or what form the expansion takes.

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: 'Get the user (by user ID) belonging to the current organization', plus the underlying HTTP path. It does not, however, distinguish this from close siblings such as identity_get_user_info_in_organization, identity_get_user_org_info, or provider_get_user, nor does it reconcile the name's 'any organization' with the body's 'current organization'.

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?

It opens with an explicit '[DEPRECATED]' marker and a 'Use this API instead: /scim/v2/Users' pointer, and the access-policy table states which roles are permitted. The gap is that the recommended replacement is a raw HTTP path, not a sibling tool name, and the description never says whether this tool still functions or under what conditions it should be preferred.

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