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

With no annotations, the description carries the full disclosure burden, and it does disclose the shape of the returned content (input specs, output specs, assumptions, tables). However, it never states that this is a non-mutating metadata read, nor whether the returned assumptions/tables reflect a specific tax year or version. Useful but not full behavioral coverage for an annotation-free tool.

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 tight sentence that front-loads the three things returned. Nothing is redundant. It is a sentence fragment rather than a complete clause, and the parenthetical '(with units, ranges and defaults)' is the only detail that earns extra length.

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 zero-parameter metadata tool with no output schema, the description tells the agent what it will get back in enough detail to decide whether calling it is worthwhile. The remaining gap is sequencing relative to 'calculate', which is a usage-guidance issue rather than a completeness one.

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?

The tool takes zero parameters, so the baseline of 4 applies. The description correctly frames the payload as a self-contained description of a calculator contract rather than implying any configuration is required.

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 the specific resource (this calculator) and enumerates exactly what the response contains: inputs with units/ranges/defaults, outputs, and the assumptions/tables behind them. That is clearly distinguishable from the sibling 'calculate' tool, which presumably executes the computation. It stops short of an explicit verb like 'Returns' or 'Describes', but the intent is unambiguous.

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?

The text gives no when-to-use guidance: it never says to call this before 'calculate', nor does it mention any alternative for retrieving calculator metadata. An agent must infer the ordering (describe, then calculate) from the tool name alone. The existence of the 'calculate' sibling makes explicit routing guidance the missing piece.

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