s21_get_upcoming_events

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

No annotations are provided, so the description carries the behavioral burden. 'Obtiene' implies a read-only retrieval, and the description names the data domain. However, it does not disclose output format, date-range semantics, or whether the result is aggregated from multiple sources.

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, focused sentence with no filler. It front-loads the action and mentions the key resource types. It is concise, though it could have used additional space for usage differentiation.

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 zero-parameter retrieval tool, the description is minimally adequate: an agent knows what data to expect. But without an output schema and with many similar sibling tools, there is still uncertainty about result shape and when this tool is the right choice.

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 tool has zero parameters, so the schema fully covers invocation requirements. The description does not need to explain parameters, and the baseline for a zero-parameter tool is appropriately high.

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 operation: retrieving the student's upcoming assignments, partial exams, and calendar events. It uses a specific verb and resource, and 'calendario del alumno' adds scope. However, it does not explicitly differentiate itself from overlapping siblings like s21_get_pending_tasks or s21_get_assignments.

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?

There is no guidance on when to use this tool versus the many sibling tools. No alternatives, exclusions, or contextual triggers are mentioned. The only usage signal is implied by the word 'próximas' and 'calendario'.

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