mcp2ws

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to describe any traits—such as whether it's read-only, requires authentication, has rate limits, or what it returns. The mention of 'SOAP method' is technical but doesn't clarify behavior, leaving critical gaps.

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 concise with a single sentence, but it's under-specified rather than efficiently informative. It wastes space on 'SOAP method:' without adding value, failing to front-load useful details. While brief, it doesn't earn its place effectively.

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?

Given no annotations, no output schema, and a simple tool with 0 parameters, the description is incomplete. It should explain what the tool returns (e.g., a list of currencies sorted by name) and basic usage, but it only provides a tautological label. This leaves the agent guessing about functionality.

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 input schema has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add param info, but that's acceptable here. Baseline is 4 for zero parameters, as the schema fully covers the absence of inputs.

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 'SOAP method: ListOfCurrenciesByName' is tautological—it essentially restates the tool name with 'SOAP method:' prefixed. It doesn't specify what the tool does (e.g., retrieve, list, or fetch currencies) or differentiate it from siblings like 'ListOfCurrenciesByCode'. The purpose remains vague beyond the name.

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 guidance is provided on when to use this tool versus alternatives. With siblings like 'ListOfCurrenciesByCode' and 'CurrencyName', the description offers no context, exclusions, or explicit comparisons. This leaves the agent without direction for selection.

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