list_updates

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

No annotations are provided, so the description must disclose behavioral traits. It only states what the tool retrieves, not any side effects, authentication requirements, or limits (e.g., number of updates, refresh behavior). This leaves the agent underinformed.

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 concise, front-loads the purpose with a clear verb and resource, and provides examples of content types. It wastes no words, though it could benefit from parameter documentation.

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 one undocumented parameter and no output schema or annotations, the description is incomplete. It explains the purpose adequately but omits parameter behavior and result details. For a simple tool, more is expected.

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 single parameter `refresh` (boolean) has 0% schema description coverage, and the tool description does not mention it at all. The description adds no value beyond the schema, which itself provides no meaning.

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 tool retrieves update information (recent activities) from the bell icon, listing types like material addition, assignment addition, submission, announcements. It effectively communicates the purpose and scope, though it does not explicitly distinguish from siblings like list_announcements or list_assignments.

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 provides no guidance on when to use this tool versus sibling tools (e.g., list_announcements, list_assignments). Usage context is implied (for recent updates) but no explicit when-to-use or when-not-to-use information.

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