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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is fully known. The description adds only a note about return forms, which is already covered by the output schema, so it provides minimal additional behavioral context.

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 short sentences front-loaded with the main purpose. No redundant or filler content.

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?

As a simple conversion tool with complete schema coverage, annotations, and an output schema, the description sufficiently captures the tool's function. It also explicitly mentions the dual scientific and engineering notation feature, which is valuable distinguishing context.

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 covers both n and precision with descriptions for each; schema_description_coverage is 100%. The description adds no additional parameter details, so it relies on the schema as baseline.

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 action: converting a number to scientific and engineering notation. Clearly distinguishes from sibling calculators which handle other conversions. The mention of returns (coefficient, exponent, human-readable forms) reinforces the scope.

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?

Implies usage for numeric notation conversion, which is clear given the name and description. Does not explicitly state when not to use it or mention alternatives, but the context of sibling converter tools makes the intended use obvious.

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