delete_github_app

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

The description adds context about the environment variable COOLIFY_REQUIRE_CONFIRM affecting the confirm parameter, which is beyond the schema. However, it does not disclose potential side effects or irreversibility, though deletion implies such.

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?

Two concise sentences without redundancy. The first sentence states the core purpose, and the second adds essential conditional behavior.

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 simple delete tool with 2 parameters, the description covers the core purpose and an important condition. It lacks details on return values or side effects, but given no output schema and absent annotations, it is adequate for invocation.

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 coverage is 100% with clear parameter descriptions. The description restates the conditional requirement for confirm but adds no new meaning beyond the schema.

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 explicitly states 'Delete a GitHub App configuration', clearly identifying the action and resource. This distinguishes it from sibling delete tools targeting other resources.

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 description mentions a conditional parameter requirement but provides no guidance on when to use this tool versus alternatives like other delete tools. No explicit when-not or alternative suggestions.

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