fabric_git_disconnect

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

The 'Destructive' tag adds little beyond the destructiveHint annotation. No additional details about what the disconnection entails (e.g., impact on version history, workspace state).

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?

Extremely concise and front-loaded, with no wasted words. The essential information is present, though it could be improved with a bit more context.

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 operation with no output schema, the description is too minimal. It does not explain the effect of disconnection, any side effects, or return behavior.

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 single parameter 'workspace' is already described in the input schema. The description adds no extra meaning, and schema coverage is 100%, so baseline 3 is appropriate.

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 ('Disconnect a workspace from Git') and the nature ('Destructive'), effectively distinguishing from sibling git tools like connect, commit, and initialize.

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 on when to use this tool versus alternatives such as fabric_git_connect or fabric_git_commit. The description does not mention prerequisites, consequences, or context.

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