detalle-de-oferta

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

With no annotations, the description carries the full behavioral burden: 'Devuelve' implies a safe read, and the field list partially compensates for the absent output schema. However, it says nothing about whether a session/login is required (siblings like iniciar-sesion exist), or what happens for an invalid or expired offer id.

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?

One front-loaded sentence with zero filler, and the useful payload (the returned field list) comes immediately after the verb. It is appropriately sized for a simple detail getter, though it could spend one more clause on routing.

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 one-parameter read tool with no output schema, enumerating the returned fields is the right move and mostly covers the return-value gap. The remaining holes are usage routing against buscar-ofertas and any auth/error behavior, which leaves it adequate but not complete.

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 single parameter has 100% schema description coverage including a concrete example (1886772014), so the schema does the work. The description only implies the parameter selects one offer and adds no format or constraint detail beyond it.

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?

Names a specific verb ('Devuelve') and resource ('una oferta') and enumerates the fields returned (requisitos, salario, contrato, modalidad, ciudad), so the agent knows this is a single-offer detail lookup rather than a search. It does not explicitly contrast itself with buscar-ofertas, so sibling differentiation is only implicit through 'descripción completa'.

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?

There is no statements of when to use this instead of buscar-ofertas, nor any prerequisite such as first obtaining the numeric id from a search tool. The detail-vs-list distinction is inferable but never stated, and no exclusions or error conditions are given.

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