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 only states this is a 'SOAP method', which hints at a read-only web service call but doesn't confirm safety, performance characteristics, or output format. For a tool with zero annotation coverage, this leaves critical behavioral traits (like whether it's idempotent, has rate limits, or returns structured data) completely unspecified.

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—just one phrase—and front-loaded with the key information (SOAP method). There's no wasted text, though it could be argued it's too brief given the lack of other context. For a zero-parameter tool, this brevity is mostly appropriate, earning a high score for efficiency.

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 simplicity (0 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what the tool returns (e.g., a list of continents with codes), how to interpret results, or any prerequisites. While the schema handles inputs, the output and behavioral context are missing, making it inadequate for an AI agent to use effectively without additional assumptions.

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 0 parameters with 100% schema description coverage, so the schema fully documents the lack of inputs. The description doesn't need to compensate for any parameter gaps, and the baseline for this scenario is 4. The mention of 'SOAP method' adds minimal context about the interface but doesn't detract from the parameter clarity.

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: ListOfContinentsByCode' restates the tool name with minimal added value. It indicates this is a SOAP method, which provides some technical context, but doesn't clearly state what the tool does (e.g., retrieves continent data by code). Compared to siblings like 'ListOfContinentsByName', it doesn't differentiate the 'by code' aspect 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?

No guidance is provided on when to use this tool versus alternatives. With siblings like 'ListOfContinentsByName' and 'ListOfCountryNamesGroupedByContinent', the description doesn't explain the specific use case for retrieving continents by code rather than by name or in other groupings. The SOAP method mention implies a technical context but offers no practical usage advice.

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