users

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

Annotations already indicate the tool is read-only, non-destructive, and idempotent. The description adds value by noting admin permission requirements for the 'list' action and the fallback behavior of 'from_workspace'. There is no contradiction with annotations.

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 concise and well-structured with a clear list of actions. Each line adds value. The phrase 'Actions (required params):' is slightly ambiguous as not all actions require additional params, but overall it's efficient.

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?

The description covers actions and parameters well, but lacks any indication of the return format or output structure. Without an output schema, this gap may force the agent to guess or rely on defaults. For a simple info tool, this is acceptable but not 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%, so the baseline is 3. The description adds meaning by mapping actions to required parameters (e.g., 'user_id' for 'get'), providing context beyond the enum labels. Minor inconsistency: description implies user_id is required for 'get', but schema marks it optional.

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 the tool gets user information and enumerates four specific actions (list, get, me, from_workspace) with concise explanations. It distinguishes each action's purpose, making it easy for an agent to select the right one.

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 provides explicit guidance on when to use each action, including required permissions (admin for list) and a fallback strategy (use from_workspace if list fails). This directly helps the agent decide which action to invoke.

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