get_user

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

No annotations provided, so description carries full disclosure burden. While 'Get' implies read-only, the description omits error behavior (e.g., 'not found' handling), authentication requirements, and what specific user details are returned. Lacks safety and behavioral context expected for unannotated tools.

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?

Single sentence, eight words. Front-loaded with action verb, zero redundancy. Appropriate length for the tool's simplicity.

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?

Adequate for a simple 1-parameter retrieval tool, but given no output schema exists, the description could specify what user details are returned (profile, permissions, etc.) or error conditions. Acceptable but minimal.

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% with 'id' fully documented in the schema. Description mentions 'by ID' which aligns with the parameter but adds no additional semantic value (format constraints, example IDs, relationship to other parameters). Baseline 3 appropriate given schema completeness.

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?

Clear verb (Get) and resource (user) with specific identifier (by ID). However, it fails to distinguish from sibling tools like 'get_users' (batch retrieval) or 'get_current_user' (authenticated user context).

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?

Provides no guidance on when to use this single-user lookup versus the plural 'get_users' or 'get_current_user'. The phrase 'by ID' implies usage but doesn't explicitly state selection criteria or prerequisites.

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