fusion_soap_call

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

Beyond the destructive/read-only annotations, the description discloses the envelope is built from the service contract with service-specific namespaces, parameters are sent in contract order, omitted parameters become empty elements shifting positional arguments, and read-only operations still pass through the destructive gate. This is substantial behavioral context that annotations alone do not provide.

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 warning about data change is front-loaded, each paragraph adds unique behavioral or safety information, and the Args list is compact. The namespace discussion is a little detailed but earns its place because it explains a real failure mode.

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 complex mutating tool, the description covers prerequisites, parameter behavior, safety gate, and service-specific envelope construction. An output schema exists, so return-value documentation is not required from the description, and nothing essential is missing.

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 description coverage is 0%, but the Args section explains every parameter: service gets a concrete path example, operation is sourced from fusion_soap_describe, parameters is a name/value map with ordering and omission semantics, and confirmed has a strict safety condition. This fully compensates for the schema's lack of descriptions.

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 opens with a specific verb and resource: 'Invoke any snapshotted SOAP operation.' It also references fusion_soap_describe for operation names and explicitly warns it may change data, making it easy to distinguish from sibling inspection tools such as fusion_soap_describe and fusion_soap_list_services.

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?

It provides a clear prerequisite—operation names must come from fusion_soap_describe—and states that confirmed must only be set after explicit user confirmation. It does not explicitly enumerate alternative tools or when-not-to-use conditions, but the scope ('any snapshotted SOAP operation') and the destructive gate make the usage context clear.

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