Call several Blackboard endpoints at once

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds that it uses Blackboard's own batch endpoint and that it performs GET reads in a single round trip, which aligns with the annotations. It does not cover partial-failure behavior or rate limits, but the read-only safety is well covered by annotations and the description reinforces it without contradiction.

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 two sentences with no filler. The core purpose is front-loaded, the example is embedded naturally, and the comparison to bb_raw_request is concise and useful.

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 batch GET tool with complete schema and read-only annotations, the description covers the essential context: purpose, usage scenario, and path format. It does not describe the response format, but given there is no output schema and the tool is relatively straightforward, the missing information is not critical. It is adequately complete for an agent to select and invoke it correctly.

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 100% for both parameters, so the schema already documents paths and maxChars. The description adds a concrete example path ('v1/courses/_12345_1/groups') that illustrates the version-relative format, but this is minor value beyond the schema's own examples. Baseline 3 is appropriate.

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 clearly states it fans out up to 20 GET reads in a single round trip using Blackboard's batch endpoint. It specifies the verb (GET) and the resource (batch endpoint), and distinguishes itself from the sibling bb_raw_request by emphasizing efficiency for repeated reads across courses.

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?

It provides a clear use case: 'when gathering the same data across many courses' and explicitly contrasts with repeated bb_raw_request calls, noting it is cheaper. It does not explicitly state when NOT to use it (e.g., for non-GET operations), but the GET-only constraint is implied and the comparison gives strong guidance.

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