clio_list_custom_actions

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

The description mentions routing through an API endpoint with JWT/tenant/company scope, which gives some authentication context. However, it does not disclose whether the operation is read-only, whether it returns paginated results, or any other behavioral traits like rate limits.

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 short and includes a routing detail that is likely irrelevant for tool selection. While it is concise, it lacks critical information, making the conciseness detrimental.

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?

Given that this is a list operation with an output schema, the description is incomplete. It does not specify the return format, pagination behavior, or any constraints on the list, leaving the agent without sufficient 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?

The only parameter 'arguments' is described as a 'JSON string of arguments for the connector operation', which adds no meaningful detail beyond the schema. With schema description coverage at 0%, the description should compensate but fails to explain what arguments are expected.

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 it is a 'list' operation for 'custom actions', which identifies the verb and resource. However, it does not explain what custom actions are or what the list returns, and it lacks differentiation from other list tools beyond the resource name.

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 provided on when to use this tool versus alternatives. There is no mention of prerequisites, alternatives, or context for when to select this tool over other Clio tools.

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