disconnect_ecommerce

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

The description labels the tool as a mutation and requires confirmation for execution, hinting at destructiveness. But it does not disclose side effects like loss of integration or data repercussions. With no annotations, more behavioral detail is expected.

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 a single sentence with a bracketed note, efficient and front-loaded. It wastes no words, but could be slightly more structured (e.g., separate sentence for confirmation).

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 mutation with no output schema, the description lacks essential context: prerequisites (must have active connection), effects post-disconnect, and error scenarios. This gap leaves the agent underinformed.

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% (baseline 3). The description adds value by instructing how to form the platform_type value ('Usa disconnect_ seguido del nombre de la plataforma activa'), aiding parameter selection beyond the schema enums.

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 tool disconnects e-commerce integration with specific verb 'Desconectar' and resource 'plataforma e-commerce', listing typical platforms. It distinguishes from sibling tools like 'connect_ecommerce' and 'test_ecommerce_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 implicitly indicates when to use (to disconnect) and includes a critical usage note about passing 'confirm=true' to execute the dangerous action. However, it lacks guidance on prerequisites (e.g., active connection) or alternatives.

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