clio_log_expense

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

No annotations are provided, so the description must fully disclose behavior. It only states the action without mentioning side effects, permissions, reversibility, or what happens after logging the expense. This is insufficient for an agent to understand the tool's behavior.

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 sentence with no redundancy, making it concise. However, given the complexity of 6 parameters and no other documentation, it is under-specified rather than efficiently concise, so a middle score is appropriate.

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 only a one-line description, no annotations, no output schema, and incomplete parameter documentation, the description is highly incomplete. An agent lacks essential context to invoke the tool correctly, especially considering the number of required parameters.

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 schema provides descriptions for 3 of 6 parameters (date, price, quantity), but the tool description adds no parameter information. The remaining parameters (matter_id, note, activity_description_id) are undocumented in both the schema and the description, requiring the agent to guess their meaning.

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 clearly states the tool logs an expense entry on a matter, using a specific verb and resource. However, it doesn't explicitly distinguish it from sibling tools like clio_log_time or clio_log_communication.

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?

There is no guidance on when to use this tool versus alternatives such as clio_log_time. The description only states what it does, without any contextual or exclusionary information.

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