cursadas_docente

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 only states the source 'desde zona_clases' and the listing action, which implies read-only behavior but does not disclose things like authentication requirements, whether only active courses are returned, pagination, or response characteristics. This is a minimal behavioral disclosure.

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 one concise, front-loaded sentence. It includes the action, object, and source without any fluff or repetition. Every word adds value, making it an efficient and well-structured description.

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 zero-parameter listing tool with an output schema available, the description is mostly complete. It tells the agent what is listed and from where. It doesn't specify whether the list includes all courses or only current/active ones, but that is a minor gap given the tool's simplicity and the existence of an output schema.

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?

There are zero parameters, so there is nothing for the description to explain about parameters. The schema has 100% coverage trivially. The baseline of 4 for zero-parameter tools is appropriate because no additional parameter meaning is needed.

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 'Lista' (lists) and explicitly names the resource (cursadas/comisiones del docente desde zona_clases). It clearly distinguishes this listing tool from sibling tools like detalle_cursada_docente, exportar_cursada_docente, or inscriptos_cursada_docente, which have different actions.

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 implies when to use the tool—when you need to list a teacher's courses/commissions—but it does not explicitly state alternatives, when-not-to-use, or conditions like 'use detalle_cursada_docente for a single course'. Usage context is only implicit from the listing verb.

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