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

With no annotations, the description carries the full burden and does so well: it discloses statefulness, that it establishes a baseline then retains the prior observation, that it fetches the live endpoint, and it even surfaces the cost ($0.003 USDC on Base). It does not state failure behavior or how the comparison is scoped when no baseline exists.

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?

Front-loaded with the purpose and detection list, then the differentiation and cost. Dense but every clause contributes something; the parenthetical price is terse and useful rather than filler.

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 one-parameter, no-output-schema tool with no annotations, the description covers what the tool does, what it detects, its stateful baseline requirement, and its cost. The main remaining gap is what a caller receives back (a delta/report shape), which is not documented anywhere.

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 description coverage is 0% for the single required serverUrl parameter, so the description would ideally clarify it. It implies the parameter is the live MCP endpoint to fetch and baseline ('fetches the live endpoint'), but never states the expected URL form or whether it must be reachable during the call.

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+resource — a stateful live remote-MCP monitor for tool-rug-pull and tool-poisoning risk — and enumerates the exact detections (added/removed tools, altered descriptions, risk-score changes, new high-risk capability signals). It also explicitly separates itself from a generic 'manifest diff', so an agent can distinguish it from siblings like mcp_vendor_due_diligence and mcp_payment_preflight.

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 clear timing guidance: run it before an agent reconnects or pays, and it requires a prior baseline to be meaningful. It does not explicitly name the sibling tools it should be preferred over (e.g. the manifest-diff or due-diligence tools), so it stops short of full when/when-not routing.

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