contar_normas

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

No annotations and the description adds nothing about behavior beyond the count itself. It doesn't say whether it requires auth, whether it's a live count or cached, or what triggers staleness. However, the tool is trivial (a count) with an output schema, so the burden is lighter.

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?

Single short sentence, front-loaded, zero waste.

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 an output schema present, return values need not be explained, and there are no params. The description is sufficient for a trivial count tool, though a note about catalog scope would help marginally.

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?

Zero parameters; baseline 4 per rules. The description correctly implies no filtering parameters affect the count.

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 clearly it returns the total count of norms in the catalog ('Número total de normas disponibles en el catálogo'). The verb+resource is identifiable (count of normas) and distinguishable from siblings like buscar_normativa or obtener_norma, though 'contar' being absent makes it slightly less explicit.

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?

No guidance on when to use this counting tool versus buscar_normativa or listar_valores_filtro. The agent must infer usage context entirely.

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