Get Activity Stream

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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so 'Read-only' adds little. However 'Titles and messages are fenced as untrusted text' is genuine, non-obvious safety context an agent needs when handling the output, and 'newest first' discloses ordering. No return-shape or volume limits are described.

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?

Front-loads purpose and scope, then item types, then safety note, then sibling routing — each clause earns its place with no filler. Appropriately short for a two-parameter read tool.

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?

No output schema, but the description names the item categories, ordering, and untrusted-text handling, giving a good picture of the response. It does not mention result volume or truncation behavior beyond the limit parameter, a minor gap for an open-world feed 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 coverage is 100% and both parameters carry descriptions plus a stated default (only_active_courses defaults true), so the schema does the work. The description adds no additional meaning about limit or course-activity filtering, which is acceptable at baseline 3.

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 and resource ('Get recent activity across all your courses'), enumerates the item types returned (announcements, discussion replies, graded submissions, messages), and specifies ordering ('newest first'). Clearly differentiated from get_activity_stream_summary and get_course_activity_stream by scope.

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?

Explicitly routes the agent: counts-only goes to get_activity_stream_summary, single-course goes to get_course_activity_stream. The remaining case (cross-course feed) is exactly this tool, so selection is fully determined.

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