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 behavioral traits—such as whether it's a read-only lookup, requires authentication, has rate limits, or returns structured data. The mention of 'SOAP method' is technical but doesn't clarify the tool's behavior or output.

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 with just two words, but this brevity results in under-specification rather than effective communication. However, based on the scoring rubric, conciseness is scored independently, and this is front-loaded with no wasted words, earning a high score for structure alone.

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 complexity (1 parameter, no annotations, no output schema), the description is incomplete. It doesn't explain the tool's purpose, usage, behavior, or parameters, failing to provide enough context for an AI agent to use it effectively among its siblings.

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 schema description coverage is 0%, and the description adds no meaning to the single parameter 'sISOCode'. It doesn't explain what the parameter represents (e.g., ISO language code), its format, or valid values, leaving the parameter undocumented.

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: LanguageName' restates the tool name without explaining what it does. It doesn't specify the action (e.g., retrieve, convert, validate) or the resource involved (e.g., language name from ISO code). This is a tautology that provides minimal clarity beyond the name itself.

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 its many siblings (e.g., LanguageISOCode, ListOfLanguagesByCode). The description doesn't indicate the context, prerequisites, or alternatives, leaving the agent with no usage direction.

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