List activities

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so safety and mutability are covered. The description usefully adds the "newest first" ordering, which annotations cannot express. However it does not explain pagination/backfill behavior (the `since` cursor), what the stream returns, or scope limits of the caller's visibility.

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 first sentence is front-loaded and efficient, but the bare "GET /ocs/v2.php/apps/activity/api/v2/activity" line conveys nothing actionable to an agent selecting or invoking the tool and occupies roughly a third of the text. Parenthetical appending the filter advice to the main clause hurts scannability.

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 4-parameter read tool with 0% schema coverage and no output schema, the description should describe the shape of an activity entry and define the `since` cursor; neither is present. The endpoint path is not a substitute for contract detail, so an agent could call this correctly for the simple case but would be guessing on incremental fetching.

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 and largely fails: it clarifies only `object_type` ("files") and `object_id` in passing, while `limit` (default 50) and especially `since` (integer, nullable) are left completely unexplained — an agent cannot tell whether `since` is a timestamp, an activity id, or a page token. Two of four parameters remain opaque.

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?

"Read the activity stream, newest first" names a specific verb and resource, and the note about narrowing to one object distinguishes the unfiltered vs filtered modes. No sibling overlaps in scope (list_notifications, list_files, list_events all cover different resources), so the tool is identifiable, though it never explicitly contrasts with them.

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?

It gives a concrete condition for the filtered mode ("object_type=\"files\" with a file id") but says nothing about when to prefer this tool over nextcloud_list_notifications, nextcloud_list_files, or nextcloud_list_events, which is a real risk of confusion in an 80-tool list. Usage is implied by the resource name rather than guided.

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