mcp2ws

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides minimal information. 'SOAP method' indicates the protocol but doesn't describe what the tool returns (continent list format), whether it's a read operation, potential errors, or any behavioral characteristics. The description fails to compensate for the lack of annotations.

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 concise (5 words) but under-specified rather than efficiently informative. While it doesn't waste words, it also doesn't provide enough meaningful content. The single sentence structure is clear but lacks the substantive information needed for the agent to understand the tool's purpose and behavior.

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 apparent simplicity (no parameters) but lack of annotations and output schema, the description is insufficiently complete. For a tool that presumably returns continent data, the description should at minimum explain what kind of data is returned and the basic operation. The current description leaves too many open questions about the tool's behavior and output.

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 schema description coverage is 100%. The description doesn't need to explain parameters since none exist. While it could theoretically mention that no inputs are required, the absence of parameters makes this dimension straightforward - the description doesn't need to compensate for any parameter documentation gaps.

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: ListOfContinentsByName' is tautological - it essentially restates the tool name with a protocol prefix. It doesn't specify what the tool actually does (e.g., 'Retrieve a list of continents sorted alphabetically by name'). While it distinguishes from some siblings by mentioning 'ByName', it doesn't clarify the fundamental purpose beyond what's already in 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?

The description provides no guidance on when to use this tool versus alternatives. There's no mention of when this tool is appropriate, when to choose it over other continent-related tools like 'ListOfContinentsByCode', or any prerequisites for its use. The agent receives zero usage context from the description.

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