Catálogo completo de entidades supervisadas

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds valuable behavioral context: data is cached for 24 hours, responses are paginated, and the raw dump is never returned. This goes beyond what annotations provide and helps set expectations about response size and freshness.

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 two sentences, front-loaded with the main purpose, and every phrase adds value: entity catalog, record count, filters, caching, and pagination. There is no redundancy or wasted words.

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 presence of an output schema and annotations, the description covers essential operational aspects: filters, caching, and pagination. It omits return format details, but those are presumably in the output schema. The 24h cache and anti-raw-dump notes are particularly useful for agents managing expectations.

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 only 40% (limit and offset), leaving nombre, tipo_entidad, and estado without schema descriptions. The description clarifies that these three parameters act as filters, which is useful, but it does not specify matching behavior (e.g., exact vs partial) or the meaning of estado values beyond the enum.

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 clearly identifies the resource as a catalog of all CMF supervised entities, with filters by name, type, and status. It lacks an explicit verb like 'list' or 'search' and does not distinguish itself from sibling tools such as cmf_buscar_entidad, so it falls short of a 5.

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 is for fetching filtered, paginated views of the full catalog, but it does not explicitly state when to prefer it over alternatives like cmf_buscar_entidad or cmf_listar_entidades. No exclusions or alternative comparisons are provided.

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