Get Organization User Profile

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

With no annotations provided, the description carries the transparency burden. It explicitly says 'Read' indicating a read-only operation and includes an authorization requirement, which is useful. It does not cover edge cases like invalid IDs, but for a simple read operation this is adequate.

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?

The description is two sentences, front-loaded with the core purpose and immediately followed by the permission requirement and helpful Chinese intents. Every sentence earns its place with no redundancy or fluff.

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 simple single-user get operation with one parameter and no output schema, the description is fairly complete. It states the fields included in the profile, which gives an agent a good sense of the return value, and it notes the required permission. It could elaborate on error behavior, but this is not critical for a basic fetch tool.

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 input schema already fully describes the single parameter (userIdOrPrincipalName) with a clear description. The tool description adds no extra parameter-level details beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states it reads a tenant user profile and lists content fields (job title, department, contact fields). It is distinguishable from siblings like users_list or users_search by focusing on a single profile, but it does not explicitly contrast with these alternatives.

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?

The description mentions a required permission (delegated User.Read.All) and provides Chinese intent examples, which imply usage scenarios. However, it does not explicitly say when to use this tool over users_get_manager, users_list, or users_search, leaving the usage guidance somewhat implicit.

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