obtener_parametros

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

There are no annotations, so the description carries the behavioral burden. It discloses that the tool lists data and optionally filters, but it does not describe pagination, response format, filter matching behavior, or side effects. For a simple read-only listing toul this is partially sufficient but still leaves gaps.

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 with the action, resource, and optional filter upfront. Every word adds value and there is no redundant 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?

The tool is simple, has one optional parameter, and an output schema is present. The description covers the core purpose and the filter. However, with no annotations and no usage guidance, it leaves some surrounding context undocumented, though not enough to make invocation impossible.

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%, but the description adds meaning by explaining that 'dominio' is an optional filter. It does not explain the possible values, format, or exact matching behavior, though the example ('aseguradoras autorizadas') gives some context.

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 resource ('parámetros/dominos de la API') with a concrete example ('aseguradoras autorizadas'). It is clear about what the tool does, though it does not explicitly contrast with sibling tools that also return catalogs.

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 states that filtering by 'dominio' is optional, which implies the main use is listing all parameters/domains. However, it gives no explicit guidance on when to prefer this tool over similar sibling tools, nor any exclusions.

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