Find a User

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

Annotations already declare readOnlyHint=true and idempotentHint=true, covering safety. The description adds that the search is by display name or UPN/email and that the result provides a user ID for assignments. However, it does not describe behavior like multiple matches or pagination limits, though the schema covers 'top'. The added context is useful but not especially rich.

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 a single, focused sentence that starts with the action ('Find a user'), states the search method, and explains the purpose. No wasted words.

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 lookup tool with strong annotations and a fully described schema, the description explains the purpose and search criteria. It could mention that multiple matches may be returned or clarify the response shape, but since it says 'to get the user ID' it implies the return value, making it fairly complete.

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 100% and all parameters have descriptive text, so the schema already explains 'query', 'top', and 'response_format'. The description adds no extra semantic value beyond restating the query criteria. Baseline 3 applies because the schema carries the parameter documentation.

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 uses a specific verb 'Find' with a clear resource ('user') and states the explicit purpose: to get the user ID needed for task assignments and planner_list_user_tasks. This distinguishes it from sibling tools that operate on plans, tasks, or buckets rather than users.

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 implies when to use the tool: when you need a user ID for task assignments or for planner_list_user_tasks. It does not explicitly name alternatives or say when not to use it, but there is no sibling tool with an overlapping purpose, so the context is clear enough.

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