Workspace activity

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

Annotations already declare readOnlyHint=true, so 'Read only' is redundant. The description does add real value beyond the annotations: result ordering (newest first) and the fact that each entry carries the actor. It omits default/limit behavior (schema default 30, max 100), pagination, and the size/shape of the feed.

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-loaded and dense — the core purpose and ordering come first, followed by the event catalogue. The trailing fragments 'Read only. Team.' are wasteful, with 'Team' being opaque and 'Read only' duplicating the annotation.

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 aggregation tool with no output schema, the description conveys what comes back (activity entries with actors, newest first) and the two filtering dimensions. The remaining gap is limit/pagination semantics, which matters given the 100-item cap but is not described anywhere.

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 carry parameter meaning. It names two of the three parameters (project id and kind) and their optionality, but never explains limit or its 30/100 bounds, and the loose enumeration of event categories does not map cleanly onto the eight-value kind enum in the schema.

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 resource (workspace activity) and enumerates the event types it aggregates — uploads, channel changes, feedback, tasks, release ticks, link/tracker issues — with actor attribution and newest-first ordering. That clearly separates it from narrow siblings like list_feedback or release_checklist, though no sibling is named explicitly.

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 enumeration of many event categories implies this is the general 'what happened lately' feed rather than a domain-specific one, which is usable context. But there is no explicit when-to-use, when-not-to-use, or pointer to narrower alternatives such as list_feedback when only feedback is wanted.

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