get_user_info

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

No annotations provided, so description must carry full burden. It states 'Get' implying read-only, but does not disclose any side effects, permission requirements, rate limits, or error conditions. The return type is mentioned ('JSON string'), but behavioral details are lacking.

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 short and to the point, with a clear structure (purpose, args, returns). Every sentence serves a purpose, and it avoids verbosity. However, it could be more structured (e.g., bullet points or explicit sections).

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?

With an output schema present, the description does not need to detail return values, but it does not explain what 'detailed information' includes or handle edge cases. Despite low complexity (1 param), the lack of usage context and behavioral details makes it incomplete.

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 has 0% description coverage. The description adds 'user_id: The user ID', which essentially restates the parameter name. No format, example, or constraints provided. Given zero schema coverage, the description fails to compensate.

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 specifies the action ('Get') and resource ('detailed information about a specific user'), and distinguishes from sibling tools like get_current_user (current user) and get_users (list). The mention of 'user_id' parameter further clarifies scope.

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?

No guidance on when to use this tool vs alternatives (e.g., get_current_user, get_candidate). No prerequisites, exclusions, or context for when it is appropriate. The description only states what it does, leaving the agent to infer usage from the name.

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