buscar_actividad

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

No annotations are provided, so the description carries more burden for behavioral disclosure. It implies a read-only lookup and explains DENUE's SCIAN classification, but it does not mention no-match behavior, whether multiple codes may be returned, rate limits, or authentication requirements.

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 purpose is front-loaded in the first sentence, followed by useful context and parameter guidance. There is minor redundancy in repeating examples, but the description remains compact and structured.

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?

For a simple one-parameter lookup with an output schema, the description covers the tool's purpose, intended usage, and parameter meaning adequately. It could be improved by mentioning edge-case behavior when no matching SCIAN code is found.

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%, so the description must compensate for the single parameter. It defines 'descripcion' as a natural-language business type and gives useful examples like 'farmacias' and 'taller mecánico'.

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 a specific verb and resource: 'Busca el código SCIAN de una actividad económica', with clear examples such as 'tortillerías' and 'gimnasio'. It also distinguishes the tool's intended role from counting/searching businesses by explaining that it helps select the correct code first.

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?

It explicitly says to use the tool before counting or searching businesses when the word is ambiguous, which gives clear usage context. It references sibling capabilities conceptually but does not name the exact tools or specify when not to use it.

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