Get activity

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

Annotations already declare readOnlyHint=true, so the description doesn't need to restate safety. The description adds that it is 'recent' activity, hinting at a temporal scope, but does not elaborate on limits, ordering, or pagination. It is consistent but minimal in behavioral disclosure.

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 a single sentence, concise and front-loaded. It efficiently conveys the tool's output scope. However, it could be slightly more structured by separating purpose from content summary.

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?

Given no output schema, the description partially compensates by listing included activity types (status changes, comments, issues, members). However, it omits details on ordering, filtering, pagination, or date range, which are important for a feed tool. It is average in completeness.

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?

With 0% schema description coverage, the description carries full burden for parameter semantics. It mentions 'for a project', which connects the required project_id to the tool's purpose, but provides no further detail on expected format, validation, or behavior issues. This is adequate but not informative.

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 a 'recent activity feed for a project' and lists the types of activities included (status changes, comments, issues, members). It distinguishes from sibling tools that target specific entities (e.g., list_comments, list_annotations) by framing it as a unified feed.

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 usage context (for a project's activity feed) but provides no explicit guidance on when to use this tool versus siblings like list_comments or list_annotations. It does not mention prerequisites, alternatives, or when not to use it.

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