Xoay secret API key hiện tại

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

The annotations already declare destructive=true, non-idempotent and openWorld, so the safety bar is lower, yet the description adds genuinely useful operational context: rotation is authenticated via the X-Client-Secret header and must be followed by updating MONAPAY_CLIENT_SECRET and restarting. It does not spell out what happens to the old key or on partial failure.

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?

Front-loaded with the trigger condition, and only two sentences are used. The bilingual duplication roughly doubles the text for identical meaning, which is a minor cost rather than bloat.

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?

Covers trigger, credential and required follow-up, which is most of what an agent needs. However, with no output schema present, the description should say whether the response returns the new secret value — for a rotate operation that is a meaningful omission.

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?

Zero parameters, so the baseline is 4. The description adds a little value by noting the X-Client-Secret header is the implicit credential used for the call, which the empty schema does not convey.

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?

States a specific verb and resource ('rotate the current API key secret'), and the word 'current' implicitly distinguishes it from a fresh-key sibling like monapay_generate_key. Clear enough that an agent knows what it does without opening anything else, though it never names the sibling explicitly.

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?

Gives a concrete triggering condition ('use when the secret is suspected leaked'), which is more than most definitions offer. It does not state when NOT to use it or point to an alternative for non-exposure cases, so it stops short of full routing guidance.

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