db_setup_scan

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

Discloses read-only operation over SSH, redaction of previews, and that password is held server-side to prevent leakage. No annotation provided, so description carries the burden; it does well but could mention error handling.

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?

Four sentences, no wasted words. Front-loaded with purpose, then behavior, then workflow, then safety note. Efficient and well-structured.

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?

Explains return format (redacted previews + token) and workflow. No output schema, but description compensates. Could mention prerequisites like SSH access, but adequate for complexity.

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 covers all parameters with descriptions (100% coverage). Description adds context like 'scan common web roots' for search_path but does not significantly deepen understanding beyond schema. Baseline 3 applies.

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 verb 'Discover' and resource 'DB credentials', specifies sources (.env, DATABASE_URL, wp-config.php, docker env), and distinguishes from sibling db_setup_save which is the follow-up step.

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 mentions next step 'call db_setup_save with the chosen token' and indicates read-only nature. Does not explicitly list when not to use or compare with other tools, but context is clear.

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