Listar tareas DUTIC

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

No annotations are provided, so the description must disclose behavioral traits. It mentions speed differences but does not state whether the operation is read-only, requires authentication, or has any side effects. Crucial safety info is missing.

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?

Three front-loaded sentences concisely state purpose and scope behaviors without wasted words. Efficient and clear.

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?

Despite 3 parameters and no output schema, the description does not explain the return format, pagination, or what fields are included in results. With no annotations to supplement, this is a significant gap.

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 67% (detailed and onlyHidden have descriptions). The description adds useful context for the 'scope' parameter but does not elaborate on the other parameters beyond what the schema already says. This meets the baseline for high coverage.

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 tasks from the virtual classroom, specifying two scopes ('upcoming' and 'all') and their behaviors. However, it does not explicitly distinguish this tool from siblings like 'dutic_get_course_tasks' or 'dutic_list_courses'.

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?

Provides guidance on when to use each scope (e.g., 'upcoming' is fast, 'all' includes hidden tasks) but no direction on when to prefer this tool over alternatives or when not to use it.

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