Exact number theory

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

No annotations provided; description only mentions BigInt for precision, but lacks disclosure of performance, limits, side effects, or other behavioral traits.

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?

Extremely concise at 7 words, no wasted text, but could include more useful information without becoming verbose.

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 no output schema, an enum of 7 operations, and no annotations, the description is too minimal to fully inform an agent about tool behavior and 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 describes two parameters with 50% coverage (only 'values' has a note on string usage). Description adds no extra meaning to 'operation' or parameter details.

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?

Clearly states verb 'run' and resource 'exact integer operations using BigInt', distinguishing it from siblings like arithmetic or calculus which deal with floating-point or calculus.

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 use for exact integer math with BigInt, but provides no explicit guidance on when to use versus alternatives like arithmetic or calculate.

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