detalle_fuente

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

No annotations are provided, so the description carries the burden. 'Ver detalle' implies a read-only operation, but it does not disclose what the detail contains, error behavior, or whether any authorization is needed. For a simple retrieval tool, this is adequate but not rich.

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 a single, short, front-loaded sentence with no filler or redundancy. Every word contributes to explaining the tool's purpose and usage.

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 one-parameter tool with no output schema and no annotations, the description covers the essential aspects: what it does and where the input comes from. It does not describe the return format, but 'detalle' reasonably implies a detailed object, making it sufficient for this simple tool.

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 coverage is 0%, but the description adds meaning by stating that the ID is the one returned by 'buscar_fuentes', which clarifies the provenance and expected value of the 'id' parameter beyond the bare 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?

The description uses a specific verb ('Ver') and resource ('detalle de una fuente pública') and explicitly ties the ID to the sibling tool 'buscar_fuentes', making the purpose clear and distinguishing it from the search 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?

It clearly implies the tool should be used after obtaining an ID from 'buscar_fuentes', providing useful context. It does not explicitly state when not to use it, but the reference to the sibling tool gives sufficient guidance for a simple detail lookup.

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