s21_get_assignments

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

With no annotations provided, the description carries the behavioral transparency burden. It adds useful behavioral details: the returned consignas are cleaned and provided in readable Markdown, and the response includes dates and rubrics. 'Obtiene' also clearly implies a read-only operation, though it does not discuss errors, permissions, or pagination.

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, information-dense sentence that front-loads the main purpose and lists the key return contents. There is no filler or repetition of schema details.

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 retrieval tool, the description adequately covers what the agent gets back: specific TPs, due dates, cleaned Markdown consignas, and rubrics. Since there is no output schema, this list of returned content is helpful, though it could still be richer about response shape or edge cases like missing rubrics.

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 already documents both parameters with 100% coverage, so the baseline of 3 applies. The description's mention of 'consignas limpias en Markdown' loosely echoes the clean_content parameter, but it does not add meaning beyond what the schema already states.

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 names a specific verb and resource: it retrieves Trabajos Prácticos (TP1-TP4), delivery dates, clean Markdown instructions, and rubrics. This clearly distinguishes it from siblings like s21_get_pending_tasks or s21_get_syllabus by specifying exactly which assignment data is returned.

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 purpose implicitly signals when to use it: when assignment details, due dates, instructions, or rubrics for the TPs are needed. However, it does not explicitly state when not to use it or how it differs from related tools such as s21_get_pending_tasks, s21_get_upcoming_events, or s21_get_modules.

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