getUser

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

With no annotations available, the description must disclose behavioral traits but only says 'Detail user', which implies a read operation. It does not explicitly state read-only behavior, permission requirements, error handling, or any side effects. The two-word phrase offers minimal 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 short and under-specified, consisting of only 'Detalhar usuário'. While concise, it is not appropriately structured; it is a phrase rather than a complete sentence and loses informational value. This is under-specification, not effective conciseness.

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?

The tool is a simple getter with one parameter and an output schema, so it doesn't need to explain return values. However, with no annotations, the description provides no usage context, behavioral notes, or error handling. It is minimally viable but inadequate for an agent to make informed invocation decisions.

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 has one parameter 'id' with 0% description coverage, so the description must compensate. However, the description does not mention the parameter at all, its meaning, or its format. The agent must rely solely on the schema field name 'id' and integer type, with no added semantic information.

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 'Detalhar usuário' (Detail user) clearly identifies the tool as retrieving user details, with a specific verb and resource. It distinguishes from sibling tools by focusing on the 'user' entity, though it does not explicitly differentiate its behavior from other getters. The purpose is clear but lacks specifics on what details are returned.

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 any prerequisites, context for use, or relationships with sibling tools like getAccount or getTransaction. Usage context is entirely absent.

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