blackboard_get_course_gradebook

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered. The description earns credit for adding behavior beyond that: it preserves null values and zero scores and deliberately does not compute weightings or averages, which materially shapes how an agent should interpret results.

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 with no filler; the aggregation scope is front-loaded and the negative constraint follows immediately. Appropriately sized for a single-parameter read tool.

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 read-only aggregation tool with no output schema, the description covers what is combined and what is deliberately not computed. It omits what the combined structure looks like and how the courseId maps to a section, leaving a modest gap for an agent needing to interpret the result.

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?

There is one required parameter with 0% schema description coverage, so the description must carry the load and it does not mention courseId at all. The schema's pattern constraint (^_\d+_\d+$) is left unexplained, so an agent gets no help forming a valid identifier.

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 action (joining grades, columns and categories) on a specific resource (the section's gradebook), which is clearer than the tautological name alone. However, it never distinguishes itself from close siblings like blackboard_get_grades, blackboard_get_grade_columns, or blackboard_get_grade_categories, leaving an agent to infer that this is the aggregating view.

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 'no calcula ponderaciones ni promedios' usefully signals when not to expect computed scores, and 'Une ... de la sección' implies when to use it as the combined view. But no alternative sibling is named and no prerequisite (e.g., enrollment, valid courseId) is stated, so the routing guidance is implied rather than explicit.

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