get-user

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

The description adds behavioral context about permission requirements and visibility, but lacks details on return format, error behavior, or side effects. Since no annotations are provided, the description carries the full burden and could be more thorough.

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 sentence that efficiently conveys the core purpose and two key constraints (visibility, permission). No unnecessary words or repetition.

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?

Given no output schema, the description omits what the tool returns and potential error conditions. For a simple read tool, this is acceptable but not fully 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?

The single parameter userId is defined in the schema with type string and length constraints, but the description adds no explanation of what the userId represents (e.g., format, source). With 0% schema description coverage, the description should compensate but does not.

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 one user, specifies the required permission (okta.users.read), and the visibility condition (visible to the connected Okta administrator). Among sibling tools like list-users and search-users, this distinguishes itself by targeting a single user retrieval.

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 context on when to use (requires specific permission, visible user) but does not explicitly mention when not to use or name alternative tools. However, the permission and visibility conditions give practical guidance.

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