Ver trabajos prácticos

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 states the tool returns data but does not disclose any behavioral traits such as idempotency, side effects, permissions, or rate limits. The word 'Devuelve' implies a read operation, but that is not explicitly confirmed.

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: first describes the output, second gives usage guidance. Both are front-loaded and to the point. No redundant or irrelevant 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?

Given the tool has 2 parameters and no output schema, the description mentions the output fields (consigna, fecha de entrega, delivery status) but does not provide a concrete structure or format. For a simple retrieval, it is adequate but could specify the exact output format or any limitations.

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 100%, so the baseline is 3. The tool description does not add any extra meaning beyond what the parameter descriptions already provide (courseid from listar_materias, solo_pendientes for filtering). It merely mentions output fields but not parameter details.

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 verb 'Devuelve' (returns) and the resource 'trabajos prácticos' (practical works), specifying the key output fields: assignment, due date, and delivery status. This distinguishes it from sibling tools like 'listar_materias' or 'ver_contenido_materia' which serve different purposes.

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 explicitly provides usage scenarios: 'Usá esta herramienta cuando pregunten por un TP puntual, por la consigna de una entrega o por qué les falta entregar en una materia.' This gives clear guidance on when to use the tool.

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