alumnos_cursada_docente

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

With no annotations provided, the description carries the full burden. It describes what the tool does (reads a URL and returns a list) and what fields are returned, giving transparency into the output. It does not mention authentication, rate limits, or error behavior, but for a simple read/list operation the disclosure is adequate.

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, directly-worded sentence that fronts the primary action and resource, then provides the input format and output fields. No unnecessary words or repetition.

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 the tool's simplicity (one parameter, list output) and the presence of an output schema, the description is complete. It covers the input source format and the meaningful return fields, which is sufficient for an agent to select and invoke the tool 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?

The schema provides only a 'url' parameter with no description. The tool description compensates fully by specifying the exact URL patterns accepted (zona_clases/home/<hash> or asistencias/<hash>) and what data is extracted from them. This adds significant meaning 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 clearly states the tool lists students from a course using a specific URL from zona_clases/home/<hash> or asistencias/<hash>, and enumerates the returned fields (nombre, legajo, hash interno, presente). This specific verb and resource scope distinguish it from sibling tools like inscriptos_cursada_docente or detalle_cursada_docente.

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 provides a clear trigger: use when you have a URL from zona_clases/home/<hash> or asistencias/<hash>. The mention of 'presente para la clase mostrada' implies this is for a specific class session, differentiating it from enrollment lists. However, it does not explicitly name alternatives or say 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.