blackboard_export_course_agenda

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

Annotations declare a non-read-only, non-idempotent, open-world write. The description adds real behavioral context beyond that: it writes to the downloads root, does not sync calendars, does not expand recurrences, and rejects failed sources unless allowPartial=true. These are meaningful operating constraints an agent cannot derive from the annotations alone.

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 tight sentences, front-loaded with the core action and followed by the constraints. No filler; each clause carries a distinct behavioral fact.

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 an export tool with no output schema and sparse parameter coverage, the description covers the essential write semantics and partial-failure behavior, but omits file naming, return value, and the date-range parameters that drive the export. Adequate but not complete.

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 only 20%, so the description must compensate. It clarifies allowPartial (the partial-failure escape hatch) and implicitly the outputDir destination ('raíz de descargas'), but says nothing about since, until, or the courseId format, leaving three of five parameters undocumented.

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?

States a specific verb and resource: saving a .ics copy of the dates returned by the agenda into the downloads root. This distinguishes it from the read-only sibling blackboard_get_course_agenda, though it does not explicitly name that sibling or the multi-course export variant.

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?

Usage is implied by 'export' semantics, and the description notes the allowPartial escape hatch for failed sources. However, it never states when to choose this over blackboard_get_course_agenda or blackboard_export_multi_course_agenda, leaving the routing to inference.

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