compare_criteriaThe criteria and any filters of the Virtual data rooms, by what they publish comparison.
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "compare_criteria"
}
}| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: not whether the comparison is read-only, what is compared, what the result looks like, or any constraints. A zero-parameter comparison tool with this text leaves the agent with no behavioral signal whatsoever.
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?
It is a single short sentence, but it is grammatically broken ("by what they publish comparison"), so brevity comes at the cost of comprehension rather than being a virtue. The agent must parse a mangled clause to extract any meaning.
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?
For a no-parameter comparison tool with no output schema, the description must at minimum explain what is being compared and against what, and it does not. The fragment is insufficient to call the tool correctly or to prefer it over its two 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 tool takes zero parameters, so there is no parameter semantics to explain; the baseline of 4 applies. The description adds nothing here, but nothing is missing either.
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 is a garbled fragment: "The criteria and any filters of the Virtual data rooms, by what they publish comparison." It gestures at a comparison of VDR criteria and filters but never states a clear verb or scope, so the agent must infer the action from the tool name alone. It does not meaningfully distinguish this from the sibling tools compare_options and compare_table.
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?
There is no when-to-use guidance, no prerequisites, and no mention of the sibling alternatives (compare_options, compare_table) even though all three appear to be comparison tools the agent must choose among. The fragment implies nothing about conditions that select this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.