Get 2ools project activity

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses a key semantic guarantee: 'Actor kind is explicit; an external agent is never presented as the human account that authorized it.' This is a non-obvious behavioral trait that shapes how the agent interprets results, adding real value over the annotations.

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 two sentences with zero redundancy. The first sentence front-loads the verb and object and lists the covered activity types compactly. The second sentence adds a crucial behavioral nuance without unnecessary words. Every element earns its place.

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?

The description covers what the tool does, the scope of activity types, and a critical attribution behavior. It does not explicitly describe the return structure, but the cursor/limit parameters imply pagination, and the timeline concept is clear. Given the lack of an output schema, a bit more detail about the response format could be added, preventing a perfect 5.

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%: all three parameters (project_id, limit, cursor) have descriptive text, including defaults and max. The tool description does not add any parameter-specific semantics beyond that. Per the rubric, a baseline of 3 is appropriate when schema coverage is high.

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+resource: 'Read the attributable project timeline' and enumerates the exact scope (human work, external MCP agents, builds, versions, feedback, and workspace pins). This clearly distinguishes it from siblings like wait_for_project_activity (which waits) and get_project (which fetches a single project), so it is specific and differentiable.

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 clear context for when to use the tool: whenever a comprehensive, cross-entity activity timeline is needed. However, it does not explicitly name alternatives or exclusion conditions (e.g., 'for only feedback, use list_project_feedback'), so it falls short of the explicit when/when-not guidance that would earn a 5.

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