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

The readOnlyHint annotation already covers the safety profile, so the bar is lower. The description adds value beyond structured fields by disclosing the return shape {count, activity}, which matters because there is no output schema, and by clarifying that results include both user notes and system-generated events.

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?

Two compact sentences: the first front-loads what is listed and the scoping option, the second gives the return shape and endpoint. No filler and nothing buried.

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?

With six optional params, a nested ElasticSearch filter object, and no output schema, the description does the essential work of naming the return keys and the endpoint. It does not describe the shape of an individual activity object or the filter's relation to the other params, but nothing critical to correct invocation is missing.

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%, with pagination, filter syntax, sorting, and related_id all fully documented in the schema. The description only restates related_id and adds no format, default, or interaction detail beyond it, so the 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?

States a specific verb (List) and resource (activity entries), and preempts the ambiguity of 'activity' by defining it as notes plus system events like status changes and record creation. It also names the underlying endpoint (GET /activities), letting an agent distinguish it from the create_note and list_* siblings.

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 indicates the optional scoping case — one contact or job via related_id — but gives no explicit when-to-use versus alternatives (e.g., use jobnimbus_list_tasks for tasks, create_note for writing). Usage is implied by the resource scope rather than stated.

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