Ver archivos de una sección de un archivo institucional

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds real behavioral context beyond that: it returns links rather than file contents, and it discloses the 5 MB cap on the preview/download path that forces an alternative retrieval route.

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?

Two sentences, zero waste, with the return shape front-loaded ahead of the caveat about links vs. contents and the size-limit routing. Every clause carries 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?

An output schema exists, so return values need not be described; annotations carry the safety profile; the description covers the one non-obvious behavior (links, not bytes) and the size-cap constraint. Nothing an agent needs to call this correctly is missing.

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 100%, so both enums and the seccion string are already documented in the schema; baseline 3 applies. The description only reinforces that `seccion` is an id from list_archivo_secciones, without adding format or syntax detail 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?

States a specific verb and resource ('List the downloadable files (title, URL, format) in one section') and ties itself to the sibling that produces section IDs ('from list_archivo_secciones'). An agent can distinguish it from list_archivo_secciones and from the file-fetching tools without opening any schema.

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?

Gives the prerequisite path (a `seccion` id comes from list_archivo_secciones) and routes large-file retrieval away from this tool ('download large files directly'). It stops short of an explicit when-to-use/when-not statement naming download_resource, but the context is clear.

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