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

No annotations exist, so the description carries the full burden, and it does disclose the key modeling assumption that unbillable time is factored into the rate rather than ignored. It reads clearly as a stateless computation with no side effects. It doesn't state output format or currency handling, but for a pure calculator the disclosed modeling behavior is the material trait.

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 what the tool produces and followed by the question it answers and its inputs. No filler, no restatement of the title, nothing to trim.

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 no annotations and no output schema, the description must stand alone, and it does reasonably well by naming the output (an hourly or day rate) and the inputs. Minor gaps remain around units/currency and whether the rate is returned pre- or post-tax, but nothing critical for invoking a four-parameter calculator.

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 the schema already defines all four inputs; the description merely re-enumerates them in prose (target annual income, business costs, working weeks, billable hours) without adding format, units, or boundary guidance. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb ('work out') and a precise resource ('the hourly or day rate a freelancer or consultant needs to charge'), plus the framing question it answers. None of the sibling tools (break_even, ebitda, profit_margin, valuation, acquisition_affordability) compute a billing rate, so an agent can route to it unambiguously.

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?

Gives clear triggering context ('what should I charge per hour?' once unbillable time is accounted for) and names the input situation the tool expects (target income, business costs, working weeks, billable hours). It stops short of stating when NOT to use it or naming an alternative, but no sibling overlaps enough to require that.

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