Resoluciones globales por mercado

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds the market-wide, date-range scope, which is useful context beyond the annotations. However, it does not disclose other behavioral traits like pagination, response format, or what constitutes a 'resolución' in this context.

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, front-loaded sentence with no unnecessary words. However, its brevity comes at the cost of essential details, making it concise but under-specified.

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?

Given the tool has 4 optional parameters, an output schema, and no parameter descriptions, the description is far too sparse. It does not explain what the output contains, how to use tipoentidad, nor any limitations (e.g., date range constraints), so the agent lacks enough context to invoke 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?

With 0% schema coverage, the description must compensate for parameter meaning, but it only hints at the date range and market. It does not explain 'tipoentidad' at all, and the enum values ('V', 'O', 'S') are undefined, leaving most parameters semantically opaque.

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 states the tool returns resolutions for an entire market within a date range, which clearly identifies the resource (resoluciones) and scope (mercado, fechas). It distinguishes itself from entity-specific tools like cmf_empresa_resoluciones, but lacks an explicit verb and is somewhat generic.

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 provides no guidance on when to use this tool versus alternatives. It does not mention related tools such as cmf_resoluciones_cursadas or cmf_sanciones_globales, nor does it state any exclusions or prerequisites, leaving the selection decision entirely to the agent.

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