Create expense entry / flat-fee line item

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

Annotations indicate it's a write operation (readOnlyHint=false) and non-idempotent (idempotentHint=false). The description adds behavioral context by explaining the total calculation and that quantity is usually 1 for flat-fee, which goes beyond what annotations provide. However, it doesn't mention side effects like creation of multiple entries on repeat calls.

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 sentences, front-loaded with the main action, and every sentence adds value. No unnecessary text.

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 8 parameters, no output schema, and only basic annotations, the description is incomplete. It lacks explanations for many required and optional fields (e.g., expense_category_id, non_billable) and does not describe return values or behavior for repeated calls.

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 only 38% (3 of 8 parameters have descriptions). The description adds meaning for quantity (usually 1) and price (per-unit cost), but fails to explain other parameters like matter_id, user_id, expense_category_id, non_billable, and note. This leaves significant gaps for an agent to understand the full input.

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 it creates an ExpenseEntry and includes flat-fee line items. It uses a specific verb (creates) and resource (ExpenseEntry), and distinguishes from siblings like clio_create_time_entry by explicitly mentioning the calculation formula (quantity × price vs. rate × hours).

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?

The description explicitly tells when to use this tool versus the time entry tool by stating 'total = quantity × price (not rate × hours)'. This provides clear guidance on usage context.

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