disconnect_storage

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

The description explains the behavior clearly: deletes the connection, retains nothing about the storage, and leaves user data untouched. This goes beyond what annotations would provide, especially since no annotations are given.

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 concise with three sentences plus a parenthetical. Each sentence adds value: action, consequence, alternative, and prerequisite. No wasted words.

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?

Given zero parameters and an output schema for return values, the description adequately explains the tool's purpose, effect, and usage context. It is complete for the complexity level.

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 zero parameters, so the baseline is 4. The description does not add parameter information because none exist.

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' and the resource 'BYOS storage database'. It also distinguishes from the sibling tool 'disable_and_erase_storage' by specifying the different effect on data.

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 explicitly tells when to use the tool (disconnect BYOS storage) and when not to (to erase NeuroDock-hosted storage, use 'disable_and_erase_storage'). It also includes a prerequisite: 'Requires a signed-in NeuroDock account.'

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