get_user_details

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

With no annotations, the description carries the full burden. It discloses the authentication requirement and lists the returned data fields, but it does not explicitly state read-only behavior or describe the outcome if the user is not authenticated. The verb 'Fetch' implies read-only, but additional transparency about error handling or side effects would strengthen it.

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 that front-loads the verb and resource. Every word contributes value, with no filler or repetition of the tool name.

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 parameterless tool with no output schema, the description covers the essential return fields (name, email, address, delivery info, wallet balance) and the auth prerequisite. It does not address error behavior or alternative tools, but the core functionality is well-specified for a simple getter.

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?

The input schema has zero parameters, so the description has no parameter semantics to clarify. Per calibration, 0 parameters gives a baseline of 4; the description adds no unnecessary parameter detail and focuses on the tool's purpose.

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 'Fetch the logged-in user's profile (name, email, address, delivery info) and wallet balance.' This is a specific verb+resource with a clear scope, and it distinguishes itself from sibling tools such as get_wallet_balance (wallet-only) and auth_status (session check) by combining profile and wallet data.

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 mentions 'Requires authentication' as a prerequisite, which gives some usage context. However, it does not explicitly state when to prefer this tool over alternatives like get_wallet_balance for wallet-only needs or auth_status for authentication checks. The guidance is implied but lacks explicit when/when-not or alternative naming.

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