yougile_get_user

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds no additional behavioral context beyond the fact that it is a read operation; it does not mention response format, error behavior, authentication needs, or any other non-obvious traits. Since the description must add value beyond annotations, it falls short.

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, front-loaded sentence that conveys the core action, target, and input criterion with no redundancy. Every word earns its place, making it appropriately concise.

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 get tool with annotations and full parameter coverage, the description is minimally viable but lacks crucial context. Since there is no output schema, the description should clarify what 'details' entails or what the return value looks like, but it does not. It also doesn't mention behavior when the user is not found, making it incomplete for a standalone read operation.

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 schema description coverage is 100%, with the single parameter 'id' already described as 'User UUID'. The description's 'by ID' adds no new meaning beyond what the schema provides, so the baseline score of 3 applies.

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 uses a specific verb ('Get') and resource ('details of a specific user'), clearly indicating the tool's action and scope. It distinguishes itself from siblings like yougile_list_users (which returns multiple users) and yougile_delete_user (which removes a user), making the purpose unambiguous.

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 implies usage when you have a user ID and need specific user details, but it does not explicitly state when to use this tool versus alternatives such as yougile_list_users. No exclusions or alternative tool names are provided, so usage context is only implied rather than clearly stated.

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