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

Annotations already flag destructiveHint=true, and the description adds exactly the right context on top: which entries are skipped, that existing values are not cleared, that overwrite is required to replace populated fields, that it mutates report numbers, and that omitting confirm yields a non-mutating preview with counts. It also discloses the Pro-plan and ownership boundary.

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 key mental model (rates freeze at log time) followed by scope, then the safety gate, then access limits. Dense but nearly every clause carries a fact; the sentences are long and could be split for scanability.

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?

For a 5-parameter destructive mutation with no output schema, the description covers scope, side effects, preview behavior, and entitlement. The main omission is what the actual (non-preview) run returns versus the preview counts, which the agent must infer.

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 coverage is 100% and each parameter is documented, but the description still adds meaning: `from` defines the retroactive window rather than a single day, `overwrite` is explicitly contrasted with 'does not clear a value', and `confirm` is framed as preview-vs-apply rather than a mere boolean. It doesn't clarify how userId and boardId compose (AND vs. override).

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 a specific action on a specific resource: applying today's rate/cost to hours already logged on or after `from`. The 'frozen at log time' framing makes clear this is a bulk retroactive re-pricing pass rather than a rate-setting tool like set_member_rate or set_team_rate, though no sibling is named explicitly.

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?

It gives concrete inclusion/exclusion rules: hours on or after `from` that are not invoiced, not running, not on a closed day, and only empty values unless overwrite is true. It also states the confirm: true precondition and that it is a Pro feature limited to the user's own projects/team. It stops short of naming an alternative for single-entry corrections (e.g. update_time_entry).

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