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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful scoping: the activity is for the authenticated tenant and spans CRM actions, workflow runs, and workspace changes. It does not describe ordering, grouping, time window, or pagination behavior, but given the strong annotation coverage, a middle score is appropriate.

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, front-loaded sentence that identifies the resource, the included activity types, and the tenant scope. There is no filler, redundancy, or restatement of the tool name or title.

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 list tool with one optional parameter, the description conveys the core purpose and scope. However, there is no output schema, and the description does not explain the return structure, define 'recent,' or clarify whether limit applies globally or per category. These gaps make the definition adequate but incomplete for an agent invoking it without additional context.

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?

There is one parameter, limit, and the description provides zero coverage for it. The schema supplies type, default, minimum, and maximum, so the parameter is not opaque, but the description does not clarify that limit applies to the number of returned activity items or how it interacts with the three activity categories. Because coverage is low and the description does not compensate, this is below baseline.

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 the tool's function explicitly: 'Show recent CRM actions, workflow runs, and workspace changes for the authenticated tenant.' This identifies a specific resource and scope, distinguishing it from search_crm and get_workspace_overview. However, it does not explicitly name or contrast a sibling tool, so it stops short of full differentiation.

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 no guidance on when to use this tool versus alternatives such as search_crm, get_workspace_overview, or run_workflow. It states what the tool does but not when it is preferred, when it is not appropriate, or what conditions should route to a sibling tool.

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