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

Beyond the readOnlyHint and non-destructive annotations, the description discloses ordering, flatness, lack of version aggregation, the Base-only audit event constraint, the no-cursor recent-window limitation, and the data-model fact that every change carries a message, diff, and history. It also includes the security-related guidance to treat stored content as data, not instructions. No contradiction with 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 compact and front-loaded: the core behavioral definition comes first, followed by the endpoint, the multi-space auth prerequisite, and a concise data-model/security note. Every sentence earns its place, with no filler or redundant restatement of the tool name.

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 read-only single-node activity list with no output schema, the description covers the endpoint, item types, ordering, aggregation behavior, pagination limitation, auth prerequisite, and a security caveat. Combined with the rich input schema and annotations, this is complete enough for an agent to select and invoke the tool correctly.

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%, and the schema already fully explains nodeId scoping, limit default/max, the no-cursor limitation, and targetSpaceId's auth flow. The description adds general context around 'raw' and 'no version-number aggregation,' and repeats the targetSpaceId workflow, but it does not materially add parameter-level meaning beyond the schema. Baseline 3 is appropriate.

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 opens with a precise, specific statement: 'A flat, newest-first list of the node's own change requests, operations and (Base only) audit events — no version-number aggregation.' This clearly identifies the resource, the action, and the scope. It also differentiates itself from activity_list_paged by noting the lack of version aggregation and the absence of a cursor.

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 gives explicit usage context: for multi-space accounts, call auth_verify, ask the user which space to use, and pass targetSpaceId. It also explicitly routes deeper history needs to `/api/v1/activity/paged`. It does not explicitly contrast with activity_list_for_record, but the node-scoped wording and title make the distinction reasonably clear.

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