Get recent Blackboard updates

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

Annotations already declare readOnlyHint=true, and the description reinforces this with 'Read-only.' It adds the default time window (last 7 days) and the exact activity types covered, which is useful context beyond the structured data. No contradictions with annotations.

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?

Two concise sentences front-load the primary scope ('Recent Blackboard activity across all courses') and immediately enumerate content types, ending with a short read-only note. Every word earns its place with no redundancy.

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 description fully covers what the tool returns (activity types), the default behavior, and the safety profile. It omits response structure (e.g., grouping, ordering) and doesn't discuss pagination, but with a single optional parameter and no output schema, this is largely sufficient for an agent to call 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?

The schema covers the single 'since' parameter fully (ISO date, default), and the description repeats the default. With 100% schema coverage, the description adds no additional parameter semantics beyond what the schema already provides, so the 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?

States a specific verb+resource ('Get recent...') and defines the scope precisely: activity across all courses since a time point, enumerating the four types of updates included. This clearly distinguishes it from sibling tools like get_announcements or get_grades, which focus on single types.

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 a broad-overview use case (recent activity across all courses) but does not explicitly contrast with sibling tools or state when to prefer this over specialized ones. No exclusion or alternative routing is provided, leaving the agent to infer.

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