get_user_info_by_id_api_v1_users

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action without mentioning side effects, authorization requirements, rate limits, or output nature (beyond what output schema provides). The read-only nature is implied but not explicitly stated.

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, concise sentence with no redundant words. Every word is necessary to convey the basic function.

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?

Despite having an output schema, the description is too minimal for the tool's context. It fails to clarify what user information is included, how it differs from other user retrieval tools, or any essential operational details. The tool is simple but the description is inadequate.

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 description coverage is 0%, and the description adds no meaning to the 'user_id' parameter beyond its title. It does not clarify the expected format, source, or constraints of the user ID, leaving the agent to infer from the name alone.

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 says 'Get User Info By Id', which clearly conveys the verb (get), resource (user info), and identifier (id). It is not a tautology since it adds 'User Info' beyond the name. However, among sibling tools like 'get_user_by_id' and 'get_user_info_by_session_user', it does not differentiate the scope of 'user info'.

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 is provided on when to use this tool versus other similar tools such as 'get_user_by_id' or 'get_user_info_by_session_user'. The description offers no context about prerequisites, alternatives, or when not to use it.

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