blackboard_groups

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds value beyond these: 'no enrollment changes' makes the specific non-mutating promise explicit (reassuring for a groups tool where membership mutation is a common concern), and 'visible membership' discloses that only visible memberships are returned, implying restricted data scope. These go beyond the generic read-only annotation without contradicting it.

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 10-word sentence with zero filler. The verb 'Read' is front-loaded, the resource scope follows immediately, and the behavioral caveat is appended efficiently. 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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile. The description adequately covers what is read and the scope, but gaps remain: the relationship between view and group_id is undocumented, pagination semantics (limit/offset) are unaddressed, and the meaning of 'visible' in 'visible membership' is not elaborated. Adequate for a read-only tool, but not complete for a 5-parameter tool with zero schema descriptions.

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%, so the description must compensate, and it partially does: 'course groups, group sets and visible membership' map naturally to the view enum values (groups, sets, members). However, it adds no meaning for course, limit, offset, or group_id, and it does not clarify interactions such as whether view=members requires a group_id. The parameter names and schema constraints are self-explanatory enough to keep this at baseline, but the compensation is 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?

States a specific verb ('Read') and precise resources ('course groups, group sets and visible membership'), which cleanly distinguishes this from siblings like blackboard_content, blackboard_grades, and connects_groups. The phrase 'with no enrollment changes' further sharpens the scope. An agent can tell exactly which resource domain this tool covers.

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 gives clear context: it is a read-only view of groups/sets/memberships. The clause 'with no enrollment changes' implicitly provides a when-not—do not use this for modifying enrollments—though no alternative tool is named. Among siblings, none obviously handles Blackboard group enrollment mutations, so the missing routing is not a serious gap, but explicit guidance would push this to a 5.

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