Get Group Activity Stream

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

Annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds useful behavioral context beyond annotations: results are ordered newest first, and text written by others is fenced as untrusted, which is important for an agent consuming external content. It does not mention pagination or rate limits, but the added safety note is significant.

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 three compact sentences, front-loads the core purpose and content types, then adds ordering and a safety note. Every sentence carries useful information, with no wasted phrasing.

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 simple read-only tool with one fully documented parameter and no output schema, the description covers purpose, content types, ordering, and trust handling. It does not describe limits or pagination behavior, which keeps it from being fully complete, but the essentials for selection and invocation are present.

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 100%: group_id is documented as a numeric string and the schema points to list_my_groups. The description does not add parameter-specific meaning beyond what the schema already provides, so the baseline 3 applies.

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: recent activity in a group workspace, with concrete examples of what counts as activity (discussion posts, files, announcements). The 'group workspace' scope distinguishes it from siblings like get_course_activity_stream and get_activity_stream without needing to inspect schemas.

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 the tool's use case by naming the group workspace and content types, but it does not explicitly state when to choose this over alternatives such as list_group_discussions or list_group_files. It also gives no exclusions or prerequisites beyond the required group_id in the schema.

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