consultar_perfil

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It only states that the tool is a read ('Consulta'), but it does not disclose what 'consolidated' includes, permission requirements, handling of nonexistent users, or any error or response behavior. The single phrase is too thin to be transparent.

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 with no filler. It states the verb and resource directly and earns its place without redundancy or unnecessary detail.

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 simple and the schema fully documents its parameters, but there is no output schema and the description leaves 'consolidado' undefined. An agent is not told what the returned profile looks like, how empty or invalid IDs are handled, or how this differs from searching for users. This is adequate but has clear gaps.

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%: both required parameters ('idusuario' and 'tipo') already have meaningful descriptions and 'tipo' has an enum. The description adds no extra parameter-level meaning, 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 the verb 'Consulta' with a specific object ('el perfil consolidado de un usuario'), clearly identifying the resource and action. It is distinguishable from the sibling 'buscar_*' tools, which are search tools for different entity types, and from 'calcular_match'.

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 clear context: use this tool when you need a user's consolidated profile in SportLink. It does not explicitly mention when not to use it or name alternatives, but the unique 'perfil consolidado' scope makes the intended usage evident relative to the search-oriented siblings.

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