Buscar usuarios

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

No annotations are provided, so the description carries the full burden. It states the search behavior and case-insensitivity, but does not clarify whether the operation is read-only, whether it returns partial results, or how errors or empty results are handled.

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 with no unnecessary words. It conveys the essential behavior and matching semantics efficiently.

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 description is sufficient for a simple search tool, but with no output schema or annotation, it does not describe the return structure, result limits, or sorting. An agent would know what the tool does but not exactly what to expect in the response.

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 already describes the username parameter as 'Texto a buscar', and the description adds the iLike matching behavior. This is adequate but minimal; it does not explain expected length, required format, or how the search string is interpreted beyond being a partial match.

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 tool searches for users by username using a case-insensitive partial match (iLike). The verb 'Busca' and resource 'usuarios' are explicit, and the iLike qualifier distinguishes this from a simple exact-match lookup.

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 explains what the tool does but provides no explicit guidance on when to use it versus related tools like list_users. It does not mention whether this should be used for filtering, autocomplete, or as a precursor to other user operations.

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