agenda_examenes_docente

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

With no annotations, the description must carry the full burden of behavioral disclosure. It states it lists data, implying a read operation, but it does not disclose authentication requirements, scope of the 'agenda', or any potential side effects. The mention of 'desde agenda_examenes' is cryptic and adds little transparency.

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, front-loaded sentence starting with the verb 'Lista'. It conveys the core action and resource without any wasted words, making it highly concise and easy to parse.

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 tool with an output schema, the description is minimally adequate. However, it lacks context about what 'agenda_examenes' refers to and whether any filters apply, making it less complete than similar high-scoring tools that clarify scope and alternatives.

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 has zero parameters, so the baseline is 4. The description adds meaningful context by indicating 'del docente', implying the tool uses the logged-in teacher implicitly. This goes beyond the empty schema and clarifies the intended scope.

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 'Lista agenda de exámenes del docente' clearly states a specific verb (Lista) and resource (exam agenda for the teacher). It distinguishes from siblings like 'detalle_mesa_docente' and 'inscriptos_examen_docente' by focusing on the agenda view, though it does not explicitly contrast with 'mesas_examen_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?

The description provides no guidance on when to use this tool versus alternatives. It only gives the basic purpose without mentioning any prerequisites, context, or exclusions, leaving usage decisions entirely to the agent.

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