classroom_list_announcements

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

Annotations already mark the tool as read-only and open-world, so the description's main contribution is the explicit pagination contract: returns one page as {items, nextPageToken} and tells the caller to continue until nextPageToken is null. This is valuable behavioral context beyond the annotations. It does not explain fullData or announcementStates, but core behavior is disclosed.

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: the first states the purpose, the second gives the pagination loop. Every word earns its place, and there is no redundant restating of the tool name or schema.

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?

With no output schema and 0% parameter coverage, the description is incomplete for safe and correct invocation. It handles courseId and pageToken adequately, but fullData and announcementStates are completely unexplained, leaving an agent to guess their effects. The pagination instruction is helpful but does not compensate for the missing parameter semantics.

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 by explaining parameters. It implies courseId and indirectly explains pageToken through the pagination contract, but fullData, pageSize, and announcementStates are left entirely undefined. An agent would not know what fullData does or how to filter states without external knowledge.

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 states a specific verb and resource: list announcements for a course. This clearly distinguishes it from siblings like classroom_post_announcement and classroom_patch_announcement, and the pagination note adds important scope. There is no ambiguity about the core operation.

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 context is clear: this is for reading course announcements, and the description points out the one-page-at-a-time behavior. It does not explicitly mention alternatives such as post/patch, but the operation is intuitive from the name and the sibling list. No misleading usage guidance is present.

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