elleta

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

No annotations are provided, so the description must carry full behavioral disclosure. It only states the core computation, without mentioning side effects, resource usage, or safety. However, for a mathematical computation tool, it is likely read-only and non-destructive. The existence of an output schema partially compensates for missing return value details.

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 sentence of 8 words, front-loading the core action and resource. Every word is necessary; there is no redundancy. For a simple tool with one parameter and an output schema, this length is appropriate.

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 tool has one parameter and an output schema, so the description need not explain return values. However, given the complexity of the domain (elliptic curve eta-quotients) and the presence of many similar sibling tools, the description lacks examples, constraints, or cross-references. It is minimally complete but leaves gaps for less familiar users.

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 schema covers 100% of parameters (only 'E') with description 'Elliptic curve structure.' The tool description reaffirms that E is the elliptic curve but adds no additional semantic details (e.g., construction, valid types). Since schema coverage is high, the baseline is 3, and the description does not exceed that.

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 verb 'Compute' and the resource 'eta-quotients for an elliptic curve'. It distinguishes from siblings like 'eta' (general Dedekind eta) and other elliptic curve functions (ellwp, ellzeta) by specifying the exact mathematical object. The description is specific and 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?

No guidance is given on when to use this tool versus alternatives. Sibling tools include many elliptic curve functions (ellwp, ellzeta, eta), but the description does not provide any context, prerequisites, or differential advice. The agent has no information on scenario suitability.

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