consultar_cnae

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly indicates a read-only lookup (consulta) returning code and description. No side effects or special behaviors are mentioned, which is acceptable for a simple query tool.

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 consists of two short, efficient sentences with no unnecessary words. The first sentence states the core action and parameter format; the second adds a practical use case. Excellent front-loading and conciseness.

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's low complexity (one parameter, required, output schema exists), the description adequately covers purpose, parameter format, return value nature, and a typical use case. It is sufficient for a simple CNAE lookup, though could mention error conditions or data source boundaries.

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 schema coverage is 100% with a single parameter ('codigo') already described in the schema as a 7-digit string with optional punctuation. The description's mention of '7 dígitos' adds no new meaning beyond the schema, so the baseline of 3 is appropriate.

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 states the tool consults a CNAE economic activity using a 7-digit sub-class code, returning official code and description. It specifies verb and resource, but does not explicitly differentiate from the sibling tool 'buscar_cnae', which might be similar in purpose.

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 mentions the tool is useful for identifying a company's field of activity from a CNAE code, implying when to use it. However, it does not provide explicit guidance on when not to use it or mention alternative tools among the many siblings.

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