znorder

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

No annotations are provided, so the description must carry full behavioral transparency. It fails to disclose what happens on invalid inputs (e.g., non-coprime x, non-positive n), error behavior, or any side effects. The description is overly minimal.

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, clear sentence. It is concise and front-loaded with the essential information. While it could be expanded slightly for more context, it is not wasteful.

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 an output schema, so return value explanation is not mandatory. However, the description does not define 'multiplicative order,' which may be unclear to an AI agent. Given the tool's mathematical nature, a slightly more explicit definition would improve completeness.

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 coverage is 100%, with descriptions for both parameters ('Integer coprime to n.' and 'Positive integer.'). The description adds no further detail about the parameters beyond the schema, so baseline 3 applies.

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 'Compute the multiplicative order of x modulo n.' It uses a specific verb (compute) and resource (multiplicative order). There are no sibling tools with the same function, so it distinguishes itself sufficiently.

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 provides no guidance on when to use this tool or its alternatives. No mention of prerequisites beyond what's in the schema, or when not to use it. For a mathematical function, this lack of context can cause misapplication.

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