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. However, it only mentions 'SOAP method', which is a technical detail that doesn't explain what the tool does, its safety profile, permissions needed, rate limits, or output format. This is inadequate for a tool with no annotation coverage.

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 extremely brief but not concise in a helpful way; it's under-specified rather than efficiently informative. A single phrase like 'SOAP method: CurrencyName' wastes space on technical jargon without adding value, failing to front-load useful information.

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 the tool's complexity (1 parameter with no schema descriptions, no annotations, no output schema, and multiple sibling tools), the description is completely inadequate. It doesn't explain the tool's function, usage, parameters, or behavior, leaving the agent unable to understand or invoke it correctly in context.

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 1 parameter with 0% description coverage, and the tool description provides no information about the parameter's purpose, format, or constraints. Without any details on what 'sCurrencyISOCode' represents or how to use it, the description fails to compensate for the schema's lack of 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 'SOAP method: CurrencyName' is a tautology that merely restates the tool name with technical jargon. It fails to specify what the tool actually does (e.g., retrieve currency details, convert names, or validate codes) and doesn't distinguish it from sibling tools like 'ListOfCurrenciesByName' or 'CountryCurrency'. This provides no meaningful purpose statement.

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. Given siblings like 'ListOfCurrenciesByName' and 'CountryCurrency', the description offers no context, prerequisites, or exclusions. This leaves the agent with no information to make an informed selection among related tools.

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