get_user

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

The description states the return type (JSON object with user profile details) but does not disclose error behavior, permission requirements, or rate limits. As a simple read operation without annotations, it is adequate but lacks full transparency.

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 extremely concise, with a front-loaded purpose sentence followed by clear Args and Returns sections. Every word adds value.

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 low complexity (one parameter, output schema exists), the description covers the essential information. It could benefit from a brief note on error handling or authentication, but it is largely complete.

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?

With 0% schema description coverage for the sole parameter 'identifier', the description compensates by explaining it can be a numeric ID or email, with examples. This adds meaning beyond the schema.

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 the verb 'get' and resource 'user's profile', and specifies the two types of identifiers (numeric ID or email). This differentiates it from sibling tools like list_users (list all users) and get_own_profile (own profile).

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 implicitly indicates when to use the tool: when you need a specific user's profile and have their identifier. It doesn't explicitly state when not to use it, but the sibling names provide context.

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