get_user

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

No annotations provided, so the description carries full burden. It says 'Returns: User object' but reveals nothing about error behavior on a missing ID, permission/auth requirements, or whether the result is cached. For a read tool with zero annotation coverage, this is thin.

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?

Very short and front-loaded, with the Args/Returns structure easy to scan. It wastes nothing, though the terse form leaves no room for needed context.

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?

An output schema exists, so return values are covered externally. But with zero annotations, zero schema description coverage, and no auth/error guidance, the definition is incomplete for a simple but permission-sensitive retrieval call.

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%, so the description must compensate, but it only restates the schema: 'user_id: The ID of the user.' No format, source, or example of the ID is given. Output schema exists, so return values needn't be explained, but the required parameter remains undescribed.

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?

States a clear verb+resource: 'Get a user by ID.' An agent can immediately distinguish this from get_users (bulk) and create/update user operations. It doesn't explicitly name siblings, but the singular 'a user by ID' delineates it from the plural get_users.

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 when-to-use guidance, no prerequisites, no alternatives named. An agent must infer that this is the single-user fetch and get_users is the bulk variant. There is no statement of when to prefer this over search or get_self.

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