Ejemplos de URLs (API Mercado Público)

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

No annotations provided. The description mentions only that it displays examples, implying no side effects, but does not explicitly state read-only behavior or any other traits. Since the description carries the full burden, it lacks sufficient transparency.

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?

A single sentence that efficiently states the tool's purpose and what it does. It is front-loaded, with no extraneous content. Could be slightly improved with structure, but adequate.

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 tool with one parameter and no output schema, the description is fairly complete. It tells the user what the tool does and implies the output is a set of example URLs. Minor missing details like output format, but acceptable.

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 covers the parameter 'entidad' with a description and enum. The tool description does not add additional meaning beyond the schema; thus baseline 3 applies.

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 shows real examples of URLs and supported routes (JSON, XML) with their combinations to explain how to construct HTTP routes. The verb 'Muestra' and resource 'ejemplos de URLs y rutas' are specific and differentiate from sibling tools that perform actual API calls.

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 explicit guidance on when to use this tool versus alternatives. The description implies it is for learning URL construction, but fails to mention scenarios like 'when you need to see the exact format of an API endpoint' or compare with sibling tools.

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