verify_read_only_guarantees

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

With no annotations, the description details behavior: scans Python modules and PowerShell scripts for write APIs, mutating cmdlets, shell escapes, and dynamic code execution, reporting allowed operations. It does not mention performance impact or non-destructiveness, but the core behavior is clear.

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 concise: two sentences in the first paragraph and one sentence in the second, front-loading the primary purpose. Every sentence adds value without redundancy.

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 no parameters and an output schema (not shown but indicated), the description covers what the tool does and when to use it. It could be improved by stating the tool is safe/non-destructive, but overall it is complete enough for a simple verification tool.

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?

There are no parameters (zero required). Baseline 4 applies as per guidelines, and the description adds no parameter information since none exist.

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 clearly states the tool's purpose: 'Prove that this server cannot modify the machine' by scanning source code for write APIs. It distinguishes from sibling tools (all read-only info tools) by focusing on verification rather than information retrieval.

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 explicitly says when to use ('Run this if you want to confirm the guarantee'), but does not mention when not to use or provide alternative tools. However, the unique purpose suffices for a no-parameter tool.

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