disconnect_signal

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

No annotations are present, so the description carries the full burden. It only says 'Disconnect a signal' without disclosing whether the operation is destructive, requires permissions, has side effects, or returns anything. This is a critical gap for a mutation tool.

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 extremely concise (four words) but it adds almost no value over the tool name 'disconnect_signal' – it essentially restates the name in sentence form. It lacks any informative content and does not earn its place.

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?

This tool has four required parameters, no annotations, no output schema, and no parameter descriptions. The one-sentence description is woefully inadequate for an agent to understand how to invoke the tool correctly. It provides no information about parameter semantics, behavior, or expected results.

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 has four parameters (source_path, signal, target_path, method) with no descriptions, and the tool description provides zero explanation of these parameters. With 0% schema description coverage, the description was expected to compensate but completely fails to do so.

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 'Disconnect a signal' states a clear verb and resource, but it is vague and lacks context about what a 'signal' is, what disconnecting entails, or how it differs from related actions like connect_signal or remove_signal. It is more specific than a tautology but not enough to distinguish it from siblings beyond the verb itself.

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 is provided on when to use this tool, prerequisites, or alternatives. The description does not mention that connect_signal is the counterpart or any scenario where a disconnect is appropriate.

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