blackboard_get_course

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

No annotations are provided, so the description carries the full burden. It states 'Get details' but does not disclose whether the operation is read-only, what 'details' includes, any authentication requirements, or potential errors. The description adds no behavioral transparency beyond the tool's name and basic purpose.

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 a single concise sentence, front-loaded with the action and resource, and provides an example. No filler or redundant information; every word earns its place.

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?

The tool is simple with one parameter, no output schema, and no annotations. The description is minimally adequate but does not explain what 'details' means or what the return structure might be. Given the lack of output schema, the description should offer more context about the response, making it borderline but not severely lacking.

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% (courseId is fully described with pattern and example). The tool description repeats the same example '_529580_1' without adding new semantic value. Per rubric, baseline is 3 when schema covers parameters fully.

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 the tool's function: 'Get details of a specific course by its Blackboard ID'. The verb 'get' and resource 'course' are specific, and the phrase 'specific course' distinguishes it from siblings like blackboard_list_courses which retrieves multiple 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?

The description implies usage when you have a specific Blackboard course ID, but it does not explicitly state when to use this tool over alternatives or mention that list_courses should be used to obtain IDs. No exclusions or alternative references are provided, so it's only implied context.

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