clio_list_activities

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: the governed-routing constraint and 'effect: Required and must be read; Spring verifies it.' However, the approval_ref note ('when resuming a write') is boilerplate that sits awkwardly on a forced-read tool and adds mild confusion.

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 format is reasonably organized as an opening line, a routing constraint, and a compact Args block. But the first sentence is a tautology that wastes a line, and the Args section largely duplicates parameter names already present in the schema.

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?

The output schema and annotations cover return values and the safety profile, but the description still fails to state what 'activities' are, what keys the `arguments` JSON accepts, or how this tool relates to the many clio_list_* siblings. For correct invocation, an agent is left to guess at the operation-specific semantics, which is a significant gap for a 7-parameter tool.

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 the burden, and it does gloss all 7 parameters (e.g., 'project_id: Authenticated Project UUID', 'idempotency_key: Stable business-action identity'). These one-line glosses add meaning beyond bare schema names, but several are cryptic ('Exact project correlation reference', 'Project-bound connector account alias') and the critical `arguments` JSON string format is left unspecified.

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 pure restatement of the tool name ('Clio connector operation `list_activities` (platform tool `clio.list_activities`)') and never states what the tool actually does. The only substantive sentence, 'Routes only through the exact project/account governed connector authority,' is a routing constraint, not a purpose statement. An agent must infer from the name alone that this lists activities, and nothing distinguishes it from siblings like clio_list_matters or clio_list_time_entries.

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?

No guidance is given on when to use this tool versus alternatives. There are dozens of clio_list_* siblings in the same namespace, yet the description never explains what an 'activity' is or when an agent should pick this over clio_list_time_entries, clio_list_notes, or smokeball_list_activities.

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