Recursos descargables de un curso

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

No annotations are provided, so the description carries the full burden. It does not explicitly state whether the operation is read-only, requires authentication, or any limits on returned data. The implication of 'lista' suggests a read operation, but behavioral traits are insufficiently disclosed.

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 is concise and front-loaded. There is no redundant or extraneous information; every part earns its place.

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 no output schema and a single parameter, the description minimally conveys that the result includes download URLs. However, it lacks details on result structure (e.g., whether it includes file names, sizes), pagination, or ordering, leaving gaps for an AI agent to infer correctly.

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 description coverage is 0%, and the description adds no meaning to the sole parameter 'courseId'. It does not explain its purpose, format, or where to obtain it, leaving the agent to rely solely on the integer type and exclusiveMinimum constraint in 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?

The description clearly states the tool lists downloadable files/recursos of a course, including download URLs. It uses a specific verb 'Lista' and resource 'archivos/recursos descargables de un curso', effectively distinguishing it from siblings like dutic_download_file and dutic_list_course_materials.

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?

The description provides no guidance on when to use this tool versus alternatives, nor any conditions or prerequisites. It simply states what it does without context for selection among sibling tools like dutic_download_file or dutic_read_resource.

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