bncc_lookup

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

No annotations provided, so description must cover behavior. It discloses output contents (fields, prioritization layer) but does not mention error handling, case sensitivity, or prerequisites. Adequate but incomplete for a no-annotation 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?

Concise yet informative: two sentences with examples, no fluff. Well-structured and front-loaded with purpose.

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?

Coverage is high for a simple tool: explains output contents thoroughly. Lacks error behavior or return format, but these are minor given the single-parameter, read-only nature.

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 has no description for parameter 'codigo' (0% coverage). Description compensates excellently with examples ('EF06MA01') and explains code format, adding significant meaning beyond the schema.

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?

Description clearly states tool returns full record of a BNCC skill by code, with examples and details on included fields. Distinguishes from siblings like bncc_buscar (search) and bncc_listar (list) by specifying exact code lookup.

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?

Implies use for exact code lookup via example codes, but does not explicitly state when not to use or compare to alternatives like bncc_buscar or bncc_listar. Sibling names provide context but description lacks direct guidance.

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