login_keys_delete

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

With no annotations, the description must carry the full behavioral burden. It only says 'Delete' and does not disclose irreversibility, permissions, or what confirmation actually requires. The statement 'confirm: Required' conflicts with the input schema where confirm is optional with a default of false.

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 core sentence is appropriately concise and front-loaded. However, the Args section contains redundant and even contradictory text, so not every line earns its place. It is compact but not especially well-structured.

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 destructive tool with no annotations, the description omits important context like whether deletion is permanent, what the confirm parameter controls, and any required value for confirm. An output schema exists, so return values are less critical, but the operation's behavior remains under-specified.

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 compensate. It does not: 'key_id: Key id.' merely restates the schema title, and 'confirm: Required.' contradicts the schema, which does not list confirm as required. The description adds no useful meaning and provides misleading information about a parameter.

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: 'Delete a login key.' It is unambiguous and naturally distinguishes this tool from siblings like login_keys_create, login_keys_update, and login_keys_get.

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?

No guidance is given about when to use this tool versus alternatives, nor are prerequisites or destructive-action caveats mentioned. The only hint, 'confirm: Required,' is not a usage guideline and conflicts with the schema, leaving the agent without clear decision context.

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