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

No annotations exist, so the description carries the full behavioral burden, and it delivers very little. It does not say whether this is a read-only operation, whether auth or API keys are required, whether missing OCIDs error or return empty, or what 'detalle' actually contains.

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 one-line purpose is front-loaded and the Args block is compact, contributing a useful example rather than padding. Slight redundancy between the prose and the Args line keeps it from a 5.

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?

With no output schema, the description is the only place an agent could learn the shape of the returned 'detalle', but it says nothing about return fields, structure, or errors. For a lookup tool this leaves a real gap.

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 coverage is 0%, so the description must compensate, and it does: it defines ocid as an OCDS identifier and supplies a concrete example format (`ocds-dgv273-seacev3-999999`), which is meaningfully more than the schema's bare 'string'.

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: 'Devuelve el detalle de un proceso por su OCID'. An agent can distinguish this retrieve-by-identifier tool from the sibling contrataciones_buscar, though the description never names that sibling explicitly.

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?

Usage is only implied: use it when you already hold an OCID and need full detail. There is no explicit statement of when to prefer this over contrataciones_buscar or contrataciones_ultimas, nor any prerequisite or exclusion.

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