que_skill_aplica

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

No annotations are provided, so the description bears the full burden. It discloses that the tool returns a skill and cluster, but does not mention whether it has side effects, modifies state, or requires specific permissions. It implies a read-only operation but lacks explicit behavioral details.

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 concise sentences. The first states the core purpose, and the second provides usage guidance with emphasis ('PRIMERO'). No superfluous information.

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 simplicity (single parameter, no output schema), the description is complete enough. It explains what the tool does and when to use it. It could mention the output format more explicitly, but the statement that it returns 'que skill DYNAMIS invocar y el cluster fuente' is sufficient.

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 single parameter 'problema' is described in the schema with 'Descripcion del problema u objetivo'. The tool description adds that it uses the problem to return a skill and cluster, but does not add further semantics beyond the schema. Since schema coverage is 100%, a 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 that the tool returns which DYNAMIS skill to invoke and the source cluster given a problem. It uses a specific verb 'devuelve' (returns) and distinguishes itself from siblings by being a meta-index tool.

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 explicitly says 'Usalo PRIMERO cuando no sepas que skill aplica' (Use it FIRST when you don't know which skill applies), providing clear when-to-use guidance. It does not explicitly list alternatives but implies its role as a router.

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