s21_get_syllabus

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

With no annotations provided, the description carries the behavioral burden. The verb 'Obtiene' conveys a read-only fetch, which is useful, but it does not disclose output format, potential errors, permission requirements, or whether any side effects exist. It is minimally transparent for a simple retrieval tool.

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 redundant wording. The main outcome and target resource appear upfront, making it efficient for an agent 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 one-parameter retrieval tool with no output schema, the description adequately names the content returned: general program, syllabus, and teaching data. It is complete for typical use, though it could mention the response shape or prerequisites.

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%: course_id is described as 'ID de la materia en Canvas.' The description's reference to 'de una materia' aligns with the schema but adds no additional semantic detail beyond what the schema already provides.

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 states a specific action ('Obtiene') and a precise resource ('programa general, syllabus y datos docentes de una materia'). This clearly distinguishes it from sibling tools like s21_get_modules or s21_get_assignments, which target different course content.

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 implies the tool is for retrieving syllabus and teaching information, but it provides no explicit guidance on when to choose this tool over alternatives or when not to use it. No sibling comparisons or contextual conditions are given.

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