power

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

For a pure mathematical function, the description fully captures the behavior with no side effects or hidden operations. Since no annotations are provided, the description carries the burden, but the operation is straightforward and unambiguous, requiring no additional disclosure.

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, concise sentence with no unnecessary words. It is front-loaded with the key information and gets straight to the point.

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?

This is a very simple tool with an output schema present, so the description does not need to explain return values. The description fully specifies the operation, making it complete for the tool's low complexity.

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 description explicitly references 'base' and 'exponent' in the operation, providing clear semantic meaning. Since the schema has zero description coverage, this mapping is essential for understanding which parameter plays which role.

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 'Raise base to the given exponent' uses a specific verb and resource, clearly stating the exponentiation operation. It naturally distinguishes itself from sibling arithmetic tools like add, multiply, and square_root.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention any exclusions, prerequisites, or comparative scenarios where power would be preferred over other arithmetic operations.

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