df_delete_git_connection

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

Annotations already declare destructiveHint=true and readOnlyHint=false, and the description reinforces this with 'PERMANENTLY DELETES DATA IN DATAFORGE.' It adds the important context that the deletion is permanent and identifies what gets destroyed (a saved Git connection). No contradiction with annotations is present.

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 front-loaded with the destructive warning, followed by the precise action. The first sentence is somewhat redundant with the destructiveHint annotation and slightly broad, but the overall length is appropriate and every sentence serves a purpose.

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 one-parameter destructive operation, the description sufficiently tells the agent what the tool does, what resource is affected, and that the effect is permanent. It does not describe response behavior or prerequisites, but the operation is simple and no output schema exists, so this is acceptable.

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 only defines connection_id as an integer, and the description does not explicitly explain it. However, the phrase 'saved Git connection' gives enough context to infer that connection_id identifies which connection to delete. With a single obvious parameter, the gap is minor, but the description adds little direct parameter meaning.

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 saved Git connection.' The caps-lock warning is broad, but the second sentence disambiguates it clearly. This distinguishes it from other delete tools and from Git connection tools like df_update_git_connection or df_test_git_connection.

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 clearly communicates when to use the tool: when a saved Git connection needs to be deleted. It does not explicitly mention alternatives or exclusions, such as using df_update_git_connection for edits or df_test_git_connection for validation, so it stops short of full routing guidance.

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