Compare to Baseline

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds that it explains differences, implying an analytical result. However, it does not disclose potential operational behavior such as live connections or credential requirements beyond the connection parameter, which is minimal additional context.

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 a single, front-loaded sentence with no filler words, efficiently conveying the core action. Every word earns its place.

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?

While an output schema exists for return values, the description lacks usage prerequisites and parameter clarification, making it only minimally complete for a 2-parameter tool. It is adequate but has clear gaps in parameter semantics and usage guidance.

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 input schema has two parameters with 0% description coverage, and the description adds no parameter semantics. It does not explain the baseline_label parameter or how connection should be provided, leaving the agent to infer from the schema alone. The description completely fails to compensate for the low schema coverage.

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 uses the specific verb 'Compare' with the resource 'current server state to a recorded baseline' and adds the outcome 'explain the differences'. This clearly distinguishes it from sibling tools like record_baseline (which creates baselines) and snapshot (which captures state).

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?

The description implies usage when a baseline exists but provides no explicit guidance on when to prefer this tool over alternatives like analyze_server or how to first create a baseline with record_baseline. No exclusions are stated, so it is clear context but lacking explicit alternatives.

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