get_user

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — no note on what happens if the user is not found, what authentication is required, or what fields are returned.

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?

Two sentences that convey identical information; the second is pure redundancy. Nothing is front-loaded beyond the tautological first clause.

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?

For a simple single-entity lookup with annotations covering the safety profile and no output schema, the description still omits return content, not-found behavior, and permission requirements. It is functional but leaves real gaps for an agent.

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 reported as 0% for the top-level 'path' wrapper, though the nested userId does carry 'The user identifier.' The description's phrase 'using its unique identifier' mirrors what the schema already documents and adds no format, range, or lookup semantics.

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 names a verb and resource ('Get a specific user'), and the word 'specific' hints at a single-resource lookup versus the sibling collection tools. However, the second sentence simply restates the first with slightly different wording and adds no distinguishing scope, so this is adequate but vague against siblings like get_user_collection or my_account.

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?

There is no guidance about when to use this tool versus get_user_collection, my_account, or the other user-related siblings. The agent must infer that a known userId is a precondition.

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