delete_geomi_application

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the action is 'Delete,' implying a destructive operation, but does not clarify permanence, permissions required, or side effects (e.g., impact on related resources). This is a significant gap for a mutation tool with zero annotation coverage.

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 front-loaded with the core action but includes a superfluous marketing sentence that does not aid tool selection. While concise in length, the second sentence adds no operational value, reducing efficiency.

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 and no output schema, the description is insufficient. It lacks critical details like confirmation prompts, error handling, or return values, leaving the agent with incomplete operational context despite good schema coverage.

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 100%, with clear parameter descriptions in the schema. The tool description adds no additional parameter semantics beyond what the schema provides, such as format examples or interdependencies. The baseline score of 3 reflects adequate coverage from the schema alone.

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 ('Delete') and resource ('Application for your Geomi Organization'), making the purpose evident. It distinguishes itself from siblings like 'delete_geomi_api_key' and 'delete_geomi_project' by specifying the resource type. However, it includes an unnecessary marketing phrase ('Geomi is the essential toolkit for Aptos developers') that slightly dilutes focus.

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 explicit guidance is provided on when to use this tool versus alternatives. While siblings like 'get_geomi_applications' and 'update_geomi_application_name' exist, the description does not mention them or specify prerequisites, leaving usage context unclear beyond the basic action.

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