power

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

No annotations are provided, so the description carries the behavioral disclosure burden. It clearly communicates the core operation but does not mention edge cases such as negative bases with fractional exponents, overflow, NaN, or domain restrictions. For a simple pure function, the basic behavior is transparent, but the description is 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?

One sentence, no filler, and the core meaning is front-loaded. Every word contributes to understanding.

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?

For a simple two-parameter mathematical function with an output schema available, the description covers the essential invocation semantics. It would benefit from mention of edge-case behavior or when to prefer this over siblings, but the low complexity makes the absence non-critical.

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 description coverage is 0%, so the description must clarify parameter roles. It does so by mapping 'a number' to base and 'an exponent' to exponent, making the relationship between the two parameters clear. It does not add constraints or domain details, but for two clearly named numeric parameters this is adequate.

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 states a specific operation — 'Raise a number to an exponent' — which unambiguously identifies exponentiation as the tool's function. It distinguishes this tool from siblings like add, multiply, and nth_root by naming the exponent relationship.

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 its many mathematical siblings, such as square_root, nth_root, or logarithm. The description implies the obvious use case but provides no contextual direction or exclusions.

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