orders_GetOrder

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

No annotations are provided, so the description carries the full behavioral burden. It only states that this is a SOAP operation on a service with a given adapter; it does not disclose side effects, authentication requirements, error behavior, or return characteristics, though 'Get' weakly implies a read.

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 front-loaded sentence with no wasted words. It is appropriately sized, though its brevity contributes to the lack of substantive detail elsewhere.

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 simple one-parameter SOAP operation with no output schema and no annotations, the description still omits essential context: what is returned, any SOAP-specific invocation details, and expected failure modes. It identifies the service and adapter but is not complete enough for confident invocation.

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 schema has 0% description coverage for the single required parameter 'orderId', and the description adds no meaning, format, or constraints for it. The parameter name is self-explanatory, but the description does nothing to compensate for the missing schema documentation.

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 names the SOAP operation 'GetOrder' on service 'Orders' and identifies the adapter, which implies retrieval of an order. However, it does not state what the operation actually does beyond the name, nor does it explain how it differs from siblings like orders_ListOrders or orders_GetInventory.

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?

There is no guidance on when to use this operation versus alternatives such as orders_ListOrders or orders_GetInventory. The only implied usage comes from the operation name itself, with no explicit context or exclusions.

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