blackboard_get_multi_course_agenda

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

Annotations already declare readOnly/idempotent/openWorld and non-destructive; the description adds real behavioral context beyond them: the 112-day window cap, the per-course announcements included, and two explicit non-behaviors. It stops short of describing return shape or ordering rules, but adds meaningful value over the annotations.

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 dense, front-loaded sentences with no filler; the scope, limits, and exclusions are packed efficiently, though the exclusions sentence could be slightly tighter.

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?

No output schema, so the description should be self-sufficient, and it mostly is: scope, quantity limits, date cap, and exclusions are all covered. Missing only explicit mention of the since/until parameters and the per-course grouping/ordering format.

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 0%, so the description carries the burden. It clarifies courseIds semantics (by ID, 1-10, matching maxItems=10) and implies a bounded date range via 'Máximo 112 días', but never names since/until or explains their format/relationship, leaving a partial gap.

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+resource: a combined, ordered agenda over 1-10 courses selected by ID. The '1 a 10 cursos' scope clearly differentiates it from the single-course blackboard_get_course_agenda sibling, though it does not name that sibling explicitly.

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?

Gives operative constraints (max 112 days, 1-10 courses) and two exclusions ('no determina entregas pendientes', 'no mezcla secciones por nombre'), which imply when it is and isn't appropriate, but never states an explicit when-to-use condition or names an alternative tool.

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