Obtener un artículo específico

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

No annotations are present, so the description carries full responsibility for behavioral disclosure. The description only states what the tool does, without mentioning side effects (e.g., read-only), authentication needs, rate limits, or response characteristics.

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 is extremely concise (one short sentence), but it omits crucial details about parameters and usage. Conciseness is achieved at the expense of completeness, making the description under-specified.

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 lack of annotations, output schema, and the low schema description coverage, the description fails to provide sufficient context for correct tool invocation. Important details like the meaning of 'id_norma' and 'articulo' are absent, and no guidance is given on expected return values.

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?

With only 33% schema description coverage, the description adds no meaning to the parameters 'id_norma' and 'articulo', which are required but lack descriptions in both the schema and the tool description. The only parameter with schema description is 'formato', but the tool description does not reference any parameters.

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 title and description clearly state that the tool retrieves a specific article from the official LeyChile XML. This provides a specific verb-resource combination, but it does not differentiate it from sibling tools like 'obtener_norma' or 'obtener_texto_norma'.

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 is provided on when to use this tool versus alternatives such as 'obtener_norma' or 'buscar_legislacion'. The description lacks usage context, prerequisites, or exclusions.

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