obtener_adjudicacion

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

No annotations are provided, so the description carries the behavioral burden. 'Obtiene' clearly indicates a read operation rather than a mutation, but no further behavior such as error cases, access requirements, or return limitations is disclosed.

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 directly states what is retrieved and how. It contains no redundant or wasted words.

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?

This is a simple get-by-id tool with only one required parameter and an output schema, so the description does not need to explain return values. Taken together with the schema, it is sufficient for correct invocation, though it lacks sibling comparison context.

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?

Input schema coverage is 0%, and the description only says 'dado su id', which adds little beyond the parameter name 'id_adjudicación'. It does not explain the format, origin, or domain meaning of the ID.

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 states a specific verb ('obtiene') and resource ('datos de una adjudicación (proveedor adjudicado)'), making the operation and entity clear. The parenthetical distinguishes the award entity from sibling tools like obtener_proveedor and obtener_licitación.

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 phrase 'dado su id' implies this tool is for retrieving an award when its ID is known. However, it does not explicitly state when to choose this over sibling obtener_* or buscar_* tools, nor does it mention exclusions.

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