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

Annotations already establish that this is a read-only, idempotent, non-destructive, closed-world calculation. The description adds useful context about the calculation basis—after business costs and time off—but does not disclose assumptions such as tax treatment, rounding, or output format.

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 a single focused sentence with no wasted text, and the main output and basis of the calculation are front-loaded. It is appropriately sized for a simple calculator whose parameters are fully documented in the schema.

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 full schema coverage, rich read-only annotations, and no output schema, the description provides enough context: what is calculated, for whom, and which factors affect the result. Return values are implied as hourly and daily rates, and no additional behavioral explanation is needed.

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 all five parameters are already documented in the input schema. The description mentions target income, costs, time off, and hourly/day output, but adds no syntax, default, or constraint details beyond the schema.

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 gives a specific output: the hourly and daily rate a freelancer or sole trader should charge to reach a target yearly income after costs and time off. It clearly distinguishes this calculator from generic financial siblings, though it does not explicitly name alternatives.

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 implies the audience and scenario (freelancers or sole traders setting rates), but gives no explicit when-to-use guidance, exclusions, or comparison with sibling calculators. The context is clear enough to infer usage, but not to guide between alternatives.

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