list_upcoming_classesLista turmas com data_inicio futura (a partir de hoje), ordenadas por data crescente. Use isso pra responder 'que cursos têm turma marcada?' ou 'qual a próxima turma de X?'. Pra vagas em tempo real, use check_availability.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Máximo de turmas a retornar (default 20). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not mention read-only nature, authentication, or error handling, but does specify ordering and future date filter. Adequate but not exhaustive.
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 concise sentences: first describes functionality, second provides usage examples and sibling reference. Front-loaded and no superfluous content.
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?
Simple tool with one optional parameter; description covers purpose, usage, and guidance. Missing return structure details but still sufficient for correct invocation.
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 covers parameter description (limit with range and default); tool description does not add extra meaning beyond schema. Baseline score of 3 due to full schema coverage.
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?
Description clearly states it lists future classes ordered by date, and gives example queries. Differentiates from sibling check_availability.
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?
Explicitly says when to use (for scheduled classes questions) and when not to use (for vacancies, use check_availability). Provides clear usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clearly distinct purpose: course availability vs upcoming classes, detailed vs summary listings, separate tools for blog, podcast, services, teachers, radio, school info, and cross-content search. No overlapping tool descriptions.
Most tools follow a verb_noun pattern (list_, get_, check_), but 'radio_now_playing' and 'school_info' deviate slightly, and 'search' is a single verb. Nonetheless, the naming is mostly consistent and predictable.
15 tools is well-scoped for a school information server covering courses, blog, podcast, radio, services, teachers, and institutional info. Each tool serves a necessary function without redundancy.
The tool surface provides comprehensive coverage for informational queries about the school: all major content types (courses, blog, podcast, radio) have list/detail tools, real-time availability, search, and institutional info. No obvious gaps for a read-only knowledge server.