Danh sách API key

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

No annotations are provided, so the description carries the full burden. It discloses two useful behavioral facts: only prefix and status are returned, and the secret is never returned. It does not mention pagination, errors, or auth, but for a zero-parameter inspection tool this is a minor gap.

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 short and information-dense, with no filler. The Vietnamese sentence and English summary carry slightly overlapping meaning, which costs a small amount of structural efficiency, but both are useful and the overall size is appropriate.

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 list with no output schema, the description explains what the tool does, what fields it reads, and what it deliberately does not return. There is no material missing context that would prevent an agent from invoking it correctly.

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 is empty with zero parameters, so there is nothing for the description to document. The description still adds value by indicating what the returned data will contain (prefix/status, no secret), satisfying the baseline for a parameterless tool.

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 verb and resource: 'inspect existing API key metadata.' It also adds a concrete scope by saying the tool reads prefix and status but not the secret, which clearly separates it from sibling create/revoke tools like mail_api_key_create and mail_api_key_revoke.

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 first sentence gives a clear usage context: when checking an app's key, read its prefix and status. It does not explicitly name alternatives or state when not to use it, but 'existing API key metadata' plus the sibling names make the list-vs-create/revoke distinction obvious.

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