get-unread-announcements

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

The description provides basic purpose but does not disclose additional behavioral traits such as whether fetching marks announcements as read, authentication requirements, or what happens when there are no unread announcements.

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, efficient sentence that front-loads the key information without any extraneous text.

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 tool with no parameters and no output schema, the description minimally explains the purpose. However, it lacks details on scope (e.g., across courses or current course) and behavioral side effects, which could be relevant.

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?

With zero parameters, the schema fully defines them. The description adds no extra parameter meaning, but baseline is 4 due to no gaps.

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 action ('retrieve'), the resource ('announcements'), and the specific scope ('new/unread'), distinguishing it from sibling tools like get-all-announcements.

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?

While the name and description imply usage for unread announcements, there is no explicit guidance on when to use this tool versus alternatives like get-all-announcements or get-course-announcements.

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