Xoay secret API key hiện tại

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

With no annotations, the description carries the full burden and does a good job: it discloses the rotational nature of the operation, the required X-Client-Secret, and the operational consequence that MONAPAY_CLIENT_SECRET must be updated and the plugin/agent restarted. It could more explicitly state that the old secret is immediately invalidated, but the implication is strong enough.

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 compact and front-loaded with the trigger condition. Both languages add value and there is no filler; every sentence earns its place.

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 zero-parameter tool, the description covers the trigger, the mechanism, and the required post-step. However, since there is no output schema, it does not explain what the response returns—specifically how the new secret is conveyed—even though updating MONAPAY_CLIENT_SECRET implies the response provides it. This leaves an implicit gap.

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 input schema has zero parameters, so the baseline is 4. The description adds useful context about X-Client-Secret and MONAPAY_CLIENT_SECRET, though these are not formal parameters.

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 action: rotate the current API key secret after suspected exposure. It is specific about the resource (API key secret) and the trigger condition, but it does not explicitly differentiate from the sibling monapay_generate_key, so it misses the top score.

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?

It explicitly states when to use the tool ('Dùng khi secret nghi lộ' / 'after suspected exposure') and gives a mandatory follow-up step: update MONAPAY_CLIENT_SECRET and restart. It does not mention alternatives or explicit when-not-to-use conditions, so it falls short of a 5.

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