create_fee

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

With no annotations, the description adds value by explaining the date format (YYYY-MM-DD), that duration_minutes is time spent, and billable defaults. However, it does not disclose side effects (e.g., does it create a ledger entry?), idempotency, or what happens on error. The output schema exists but is not described.

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 but unstructured: it lists three parameter explanations in a run-on manner. While it is not verbose, it could be better organized (e.g., parameter descriptions in a list) and front-load the core purpose. Missing parameter explanations reduce its efficiency.

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 8 parameters, 4 required, 0% schema descriptions, and an output schema, the description is incomplete. It does not explain all required params, the return value (despite output schema existing), or how the fee fits into the broader matter workflow. More context is needed for correct usage.

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 explain parameters. It covers date, duration_minutes, and billable (3/8), but fails to explain rate, staff_id, matter_id, description, and activity_code_id. Required params like matter_id and staff_id lack any clarification, leaving ambiguity.

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 'Create a fee (time entry)', which defines the tool's verb and resource. It differentiates from sibling tools like create_expense by specifying it's for time entries. However, it does not explain what a 'fee' means in context (e.g., billable time).

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 like create_expense or update_fee. There is no mention of prerequisites (e.g., matter must exist) or scenarios where this tool is appropriate.

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