obtener_modalidades

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It clearly describes a read-only listing operation, but it does not mention any additional behavioral traits such as authentication needs, pagination, or whether the list is exhaustive. For a simple parameterless list tool this is acceptable, though not rich.

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 concise sentence that is front-loaded with the verb and object. It contains no filler, repeats no schema information, and every word contributes to understanding the tool's purpose.

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 very simple: zero parameters, an output schema exists, and the description states what is returned. The only slight gap is that it does not explain how these modalities relate to other tools or whether the list is used as an input elsewhere, but this is not necessary for invoking the tool correctly.

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 input schema has zero parameters and 100% schema description coverage, so there are no parameter semantics to explain. The description correctly focuses on the tool's purpose instead of inventing parameter details. This matches the baseline for a no-parameter tool.

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 a specific verb ('Lista') and a clear resource ('modalidades de contratación'), with illustrative examples such as 'licitación pública' and 'contratación directa'. This distinguishes it from sibling tools like obtener_categorias or obtener_parametros by specifying exactly what kind of list it returns.

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 implies the tool should be used when an agent needs the list of contracting modalities, but it does not explicitly state when to prefer it over alternatives or provide any exclusions. There is no mention of related tools such as obtener_categorias or buscar_catalogo, so the usage guidance is adequate but minimal.

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