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

Annotations already declare readOnlyHint=false, destructiveHint=true, idempotentHint=false, and openWorldHint=true. The description earns credit by adding the unit transformation (hours decimal converted to seconds before sending) and the default-resolution rules for price and user_id, which are genuine behavioral facts not in the annotations. It doesn't explain why the tool is flagged destructive (billing impact, reversibility), leaving a small gap.

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?

Front-loaded with the 'WRITE:' marker, then three dense sentences covering semantics, unit conversion, and defaults, ending with the API mapping. No filler, though the endpoint reference is only marginally useful to an agent.

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?

It covers inputs, units, and defaults well, but with 9 parameters, a mutation, no output schema, and destructive annotation, it should say more about what's returned (the presence of a 'fields' override implies a shaped response) and about the destructive/billing consequence. Adequate but with clear gaps for a write tool.

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 100%, so each parameter is already documented, including the same price and user_id default notes that appear in the description. The only meaning added beyond the schema is the hours conversion ('1.5 = 90 minutes; it is sent to Clio as seconds'), which is useful but marginal, so the baseline of 3 applies.

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 leads with a specific verb+resource ('Record ... time on a matter') and even names the underlying endpoint (POST /activities.json with type TimeEntry). It doesn't explicitly differentiate from sibling creators (calendar entry, note, task), but the resource is unambiguous enough that an agent can distinguish it without opening the schema.

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?

Clear context and useful defaults are stated: omitting price applies the firm's rate hierarchy, omitting user_id records for the token's user. It does not, however, address when to use this versus listing/updating activities, or any prerequisites beyond the implied matter_id requirement.

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