Get User

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

The description adds that this retrieves 'the authenticated user's information,' which clarifies scope beyond the read-only annotation. However, it lacks details on response format, error conditions, or rate limits, leaving behavioral gaps despite the annotation covering safety.

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, efficient sentence with no wasted words. It front-loads key information ('Get the authenticated user's information') and includes a useful detail ('including user ID') without unnecessary elaboration.

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 read operation with annotations and no parameters, the description is adequate but minimal. It lacks output details (no schema provided) and doesn't fully address usage context, making it functional but not comprehensive.

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 parameters and 100% schema coverage, no parameter details are needed. The description appropriately omits parameter information, focusing on the tool's purpose without redundancy.

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 action ('Get') and resource ('authenticated user's information including user ID'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'get_account' or 'get_payee', which also retrieve specific entity information.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., authentication context) or compare it to similar sibling tools like 'get_account' for retrieving other entity types.

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