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

No annotations are provided, so the description carries the full behavioral burden. 'Devuelve' implies a read operation and it discloses a fixed return of 20 items and 1-indexed pagination, but omits auth requirements, rate limits, ordering, and pagination limits.

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?

Very short and front-loaded, stating the return before the argument. The Args formatting is slightly raw but contains no filler.

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 simple, 1-parameter list tool with no annotations or output schema, the description covers purpose and the only parameter. It does not describe the returned item structure or any constraints, leaving some gaps for fully informed invocation.

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?

Schema description coverage is 0%, so the description must compensate. It documents the single parameter as a page number starting at 1, adding the 1-indexed base beyond the schema's title/default, but gives no valid range or page-size detail.

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?

States a specific verb and resource: returns the latest 20 published contracting processes. This distinguishes it from contrataciones_buscar (search) and contratacion_detalle (detail) by scope, though it does not explicitly name the sibling alternatives.

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?

No when-to-use guidance or alternatives are mentioned; the description only states the return. It does not indicate when to prefer this over contrataciones_buscar or contratacion_detalle.

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