rug_pull_detector__baseline_server

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

With no annotations, the description must carry the full behavioral burden. It does disclose the core effect (reads tools/list and persists a baseline) but omits what happens when a baseline already exists for the label, whether the process is spawned with inheritable privileges, and what a failure looks like.

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?

Two sentences, zero waste, with the action and the timing condition front-loaded. Nothing needs to be read twice.

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 six-parameter, nested-object tool with no output schema, the description leaves the return value and overwrite/duplicate-baseline behavior unstated. It is adequate to attempt a call but not complete.

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?

Schema coverage is 100%, so every parameter is already documented. The description adds the useful framing that command/args and url are mutually exclusive alternatives ('stdio command or Streamable HTTP URL') and that label keys the baseline, but goes no further. Baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb and resource: connect to an MCP server, read its tools/list response, and store it as the trusted baseline. An agent can tell this apart from check_server and list_baselines by the 'store as baseline' framing, though neither sibling is named.

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?

Gives a clear trigger: 'Call this once, right after you've reviewed and approved a server's tools.' That is a real when-to-use condition with an implied when-not (not for checking drift). It stops short of naming check_server as the follow-up alternative.

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