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

Annotations already establish that this is a safe, read-only, non-destructive, closed-world calculator. The description adds useful behavioral context by naming the exact conversions performed, though it omits assumptions such as month length, rounding, or unit conventions.

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 efficient sentence organized around three calculation modes. Every clause adds useful information without redundancy.

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 calculator with no required parameters, no output schema, and no schema descriptions, the definition explains the three computations adequately. However, it leaves gaps around valid input combinations, precedence when multiple parameters are supplied, and exact return values.

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 0%, so the description must carry parameter meaning. It maps loosely to all three inputs—link speed, monthly transfer, and file size at a given rate—but does not explicitly name parameters, state optionality, or confirm valid combinations.

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 clearly states the calculator's three functions: link speed to transfer volume, monthly transfer to average rate, and file transfer time estimation. It is specific about the resource and operations, though it does not explicitly differentiate itself from any sibling tools.

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 three clauses imply when to use each calculation mode, but the description does not explicitly say which parameter combinations are valid, whether parameters are optional, or when not to use the tool. Usage is inferable but not fully guided.

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