elliptic_curve_operation

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

No annotations are provided, and the description does not disclose any behavioral characteristics beyond the tool's purpose. It fails to mention safety, error behavior, or whether the operation is a read-only computation, leaving the agent without important 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?

The description is extremely concise, using only five words plus a list, and every item is informative. Although it is a fragment rather than a complete sentence, it avoids any wasted words or redundant detail.

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?

The presence of an output schema reduces the need for return-value explanations, and parameter documentation is complete. However, the description omits any guidance on edge cases or when the tool is appropriate, making it minimally sufficient for a straightforward compute tool.

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 input schema already provides full documentation for both parameters, including accepted operation values and coefficient formats. The description adds little beyond what the schema states, only loosely referring to 'rational points' without explaining its relationship to the 'gens' operation.

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 explicitly names the resource (elliptic curves) and lists several specific operations (rank, torsion, discriminant, j_invariant), distinguishing it from sibling math tools. However, it lacks a direct verb like 'computes' and 'rational points' is not an exact match for the operation enum, creating slight ambiguity.

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 description implies this tool is for elliptic curve computations but gives no explicit guidance on when to choose it over alternatives like number_theory_operation or group_operation. There are no exclusions or prerequisites mentioned, so usage context is only minimally implied.

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