blackboard_export_course_outline

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true, idempotentHint=false, so the agent knows this writes something into an open world. The description adds that the output is a *private* JSON file with structure and sources, which is real value beyond the annotations, but says nothing about where it is written, whether it overwrites, or the cost of large exports.

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?

A single compact sentence with the core action front-loaded; no filler. The semicolon-joined caveat is slightly compressed but still readable.

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?

A write tool with 5 undocumented parameters, no output schema, and no explanation of the produced artifact's location or shape. Given the complexity, the description is too thin for an agent to invoke it correctly without guessing at parameters.

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 0% across 5 parameters, so the description carries the full burden and largely fails it: it only alludes to allowPartial ('sin allowPartial') and says nothing about courseId format, maxDepth, maxItems, or outputDir.

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: 'Guarda JSON privado con estructura y fuentes de un curso' (saves a private JSON with the course's structure and sources). This distinguishes it from read-only siblings like blackboard_get_course_outline and places it among the blackboard_export_* family, though it never names a 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?

The clause 'evita exportar consultas incompletas sin allowPartial' implies the usage condition (use allowPartial when the query would otherwise be incomplete), which is useful implied guidance. But there is no explicit when-to-use/when-not framing versus blackboard_get_course_outline or the other export tools.

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