get_user_info

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

With no annotations, the description discloses the API endpoint, conditional behavior, and return fields, but does not mention authentication requirements or rate limits, which are important for a tool accessing user data.

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 clear and structured, but the extensive list of return fields makes it somewhat verbose; it could be more concise by summarizing the return type.

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 the tool's simplicity, the description covers purpose, parameter semantics, and return values adequately, though it omits error handling or authentication notes.

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 description adds significant value beyond the schema by explaining the default behavior when user_id is empty and detailing the return structure, compensating for the schema's lack of description.

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 it retrieves detailed user info via a specific API, and distinguishes itself from sibling tools (timelines, status, etc.) by focusing on user resources.

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 explains that it gets info for a specified user or the current user if user_id is empty, providing clear context for use, though it does not explicitly exclude alternative scenarios.

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