fusion_soap_list_services

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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds valuable context by clarifying that the service list is a snapshot, that operation counts are included, and that the SOAP surface extends beyond REST resources. No contradiction with annotations exists.

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 front-loaded with the essential definition in the first sentence, then adds useful context about why SOAP services matter and how snapshots are produced. The third sentence references an external CLI command, which is slightly tangential but still helps explain the snapshot origin without bloating the description.

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 zero-parameter, read-only tool with an output schema and strong annotations, the description is largely complete. It explains what is returned (services with operation counts), the pod scope, and why this tool is useful. It could be slightly stronger by explicitly routing to fusion_soap_describe for detailed service inspection, but that gap is minor given the available structured metadata.

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 tool has zero parameters and the input schema is empty, so there are no parameter semantics for the description to clarify. The baseline of 4 applies because there is no parameter information missing that the description would need to compensate for.

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 states a specific verb ('list') and resource ('SOAP services snapshotted for this pod'), and adds that operation counts are included. It clearly distinguishes itself from the sibling tools fusion_soap_describe and fusion_soap_call by focusing on the inventory of services rather than inspecting or invoking a single service.

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 implies usage: use this tool to discover available SOAP services that are not exposed through REST, especially when exploring functionality like purchase order change orders or BI Publisher catalog administration. However, it does not explicitly say when to choose this tool instead of fusion_soap_describe or fusion_soap_call, nor does it state exclusions.

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