blackboard_list_announcements

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

With no annotations provided, the description carries the full burden. It indicates a read-only action ('list') and adds a behavioral constraint ('recent'), but does not define what 'recent' means (time window, count, ordering) or disclose pagination/limits. It is transparent about being a read operation but leaves key behavioral details unstated.

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, clear sentence that immediately conveys the tool's purpose. No wasted words; it is concise and front-loaded.

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?

Given the tool's simplicity (one param, no output schema), the description is adequate but with gaps: it does not explain the meaning of 'recent', expected output format, or usage guidelines. It is not rich enough to fully compensate for missing annotations, but it is sufficient for a basic list tool.

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 described as 'Blackboard course ID' with pattern), so the schema already documents the parameter. The description adds no additional meaning about the parameter beyond 'for a course', which is already implicit. Baseline 3 applies.

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 uses a specific verb 'list' and a clear resource 'announcements' scoped to 'a course', which distinguishes it from sibling tools like list_assignments or list_contents. It is immediately obvious what the tool does.

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 ('list announcements for a course') but provides no explicit guidance on when to choose this tool over alternatives like list_contents or list_assignments, nor does it mention exclusions or prerequisites. It has clear context but lacks comparative guidance.

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