list_coursesLista TODOS os cursos ativos da escola (resumido). Opcionalmente filtra por modalidade. Modalidades: 'profissionalizante' (formação completa com DRT), 'livre' (Express, especialização curta), 'ead' (online assíncrono). Use get_course com o slug pra detalhe completo.
| Name | Required | Description | Default |
|---|---|---|---|
| modalidade | No | Filtra por modalidade (opcional). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. It discloses that data is summarized (resumido) and only active courses. Does not mention destructive behavior, and read-only nature is implied by 'Listar'. Lacks mention of pagination or rate limits, but not essential for this simple list operation.
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, no wasted words. Front-loaded with the main purpose, then optional filter and alternative tool guidance. Efficient.
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?
With one parameter and no output schema, the description adequately covers what the tool does, its filter, and when to switch to a sibling. A bit more detail on the output format (e.g., list of slugs) could help, but 'resumido' suffices. No major gaps given the tool's simplicity.
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 coverage is 100% and description adds value by explaining the modalidade filter's purpose and listing the options with brief definitions. Goes beyond the schema's enum by giving context for each value.
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 all active courses in summarized form. Distinguishes from sibling get_course by noting that get_course provides full detail. Verb 'Listar' plus resource 'cursos' is specific.
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 states when to use this tool (listing all active courses) and when to use its sibling get_course (for complete detail). Also explains optional filter parameter with enum values.
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.