hamravesh_delete_apikey

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

Description adds value by noting the tool is disabled without HAMRAVESH_ALLOW_WRITE=1 and the dry-run preview. But it doesn't disclose irreversibility or necessary permissions for a delete operation.

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 brief and front-loaded with the action. All sentences serve a purpose, though the structure could be more formal.

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 delete tool, the description is missing crucial context like permanent effects, how to obtain the id, and the role of the org parameter. Annotations are absent, leaving gaps.

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?

Only the 'id' parameter is clarified (by id, not value). The 'org' parameter receives no explanation, and schema coverage is 0%, so the description insufficiently compensates.

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 tool deletes an API key by ID, distinguishing it from create/list tools. However, it could be more explicit that this is for deletion only.

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 direct guidance on when to use this tool vs alternatives like delete_app. The disabled note implies caution but doesn't elaborate on prerequisites or contexts.

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