exchange_get_transport_service

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

There are no annotations, so the description must carry the entire behavioral burden. 'Get' implies a read-only action, but nothing is said about what a config consists of, what the response looks like, or whether any side effects or prerequisites exist. For a no-annotation tool, this is a significant transparency gap.

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 text is short and front-loaded with the key action, with no wasted words. However, it is so terse that it sacrifices useful context; it reads more like a label than a genuinely informative 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?

The tool has no output schema and no annotations, and the description does not explain the return value, the optional server input, or how 'transport service config' should be interpreted. Given a one-line description, an agent would likely need to probe or guess to use the tool correctly.

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 single 'server' parameter has zero schema description coverage and is not mentioned in the description. The agent cannot infer whether server is required, what format it should take, or its role in selecting the transport service. The description adds no parameter meaning beyond the bare schema type.

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?

States an unambiguous verb 'Get' and a specific resource, 'Transport service config', which is distinct from sibling tools like exchange_get_transport_rules. It tells an agent what object is being retrieved, though it doesn't explicitly contrast with related getters.

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?

No when-to-use or alternative guidance appears; the description is a bare statement of the operation. There is no mention of when exchange_get_transport_service should be selected over siblings like exchange_get_server or exchange_get_transport_rules, and no exclusions are given.

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