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

With no annotations, the description must fully disclose behavior, but it leaves key assumptions unexplained, such as how SECA taxes and filingStatus are applied and what exactly 'non-billable buffer drag' means. More importantly, it claims 47 working weeks while the schema's vacationWeeks parameter defaults to 4, implying 48 weeks if the year has 52, so the description conflicts with the schema's own data.

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?

One compact sentence leads with the tool's output before listing the relevant factors, with no filler. It could be structured into multiple sentences for scannability, but it remains appropriately sized.

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?

Because there is no output schema and no annotations, the description should clarify what the returned value represents, its units, and the calculation's assumptions. It does state the result is a rate, but the 47-week inconsistency, omitted filingStatus role, and lack of caveats leave the description incomplete for safe invocation.

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 83%, so the schema already documents most parameter meanings. The description adds high-level mapping of business expenses, health insurance, and non-billable time, but it adds no specific detail about filingStatus, which remains undocumented in both the schema and the description.

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 names a specific computation—solving for the minimum billable hourly rate needed to reach a target spendable cash income—and lists the main cost and tax factors. It clearly distinguishes the tool from generic siblings by its unique output, though it never names or differentiates a specific alternative tool.

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 given for when to use billable_floor versus closely related siblings such as contractor_parity, scorp_optimizer, or solo_401k_shield. There are no stated prerequisites, exclusions, or conditions; the intended usage is only implicit from the calculator-style name and description.

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