verify_setup

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

No annotations provided, but description fully explains behavior: it runs diagnostics, returns a checklist with ok/summary/checks, and interprets results (e.g., normal scenarios). No contradictions.

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?

Well-structured with bulleted checks and JSON example but includes bilingual text and some redundancy. Could be slightly more concise, but all content is relevant.

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?

Description covers all necessary context: purpose, when to use, what checks are performed, return format, and interpretation of results. No annotations or output schema needed given completeness.

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?

No parameters, so baseline is 4. Description does not need to add parameter info.

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?

Clearly states it is a diagnostic tool for verifying MCP_CAD installation. Lists specific checks (server, SolidWorks, active document) and output format. Unambiguously distinct from sibling modeling tools.

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?

Explicitly tells when to use: after install or when something seems off. Provides expected behavior for different check outcomes, e.g., red check on active document is normal, SolidWorks issue requires opening SW first.

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