clio_request

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

No annotations exist. The description only mentions routing through an endpoint but does not disclose whether the tool is read-only, destructive, idempotent, or what happens with the arguments. Minimal behavioral context.

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 (4 lines) and front-loaded with the name, but it includes technical route info that may not be useful for an agent. It could be more content-dense.

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 the tool is generic and sibling tools exist, the description lacks completeness. It does not explain the range of possible operations, return value structure (despite having output schema), or any constraints. The agent is left guessing.

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 a little meaning but does not explain what keys or values to provide. Schema coverage is 0%, so the description should compensate but does not.

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 'Clio connector operation request' but does not specify what kind of request (e.g., fetch, mutate) or which resource. Compared to sibling tools like clio_create_matter or clio_list_matters, this tool is ambiguous about its function.

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 the many specific Clio tools (e.g., clio_create_bill, clio_get_contact). It does not indicate if this is a fallback or for custom actions.

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