Get course attendance records

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description does not need to repeat those. It adds the condition about instructor usage, which is useful context. However, no additional behavioral traits (e.g., limit behavior, sorting, or error conditions) are disclosed beyond that.

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 that front-loads the primary action and scope. Every word adds value; there is no fluff or repetition.

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 simple list tool with only two parameters and no output schema, the description gives the essential purpose and scope. However, it does not describe the return structure, pagination, or how 'limit' is applied, leaving some ambiguity for the agent.

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 only 50%: courseId has a description in the schema, but the 'limit' parameter has no description. The tool description does not explain the meaning or usage of 'limit' at all. The description mentions 'per session' but does not clarify how limit interacts with sessions, leaving the parameter semantics incomplete.

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 verb 'Lists' and the resource 'attendance records', scoping it to the signed-in user within a specific course. It also lists the statuses (present/absent/late/excused) and the condition of instructor usage, which differentiates it from sibling tools like bb_get_course or bb_list_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 usage condition ('when the instructor uses Blackboard attendance') which helps the agent understand when data is available, but it does not mention any alternatives or when not to use this tool. No explicit comparison with siblings is given.

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