Setup Nginx Reverse Proxy

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

Adds context about domain verification and adaptive behavior beyond annotations, but does not disclose the destructive nature (despite destructiveHint=true) or what gets overwritten. The description gives some transparency but misses key behavioral details.

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?

Single sentence with under 20 words, front-loaded with verb and resource. Concise but slightly dense; could be structured for better clarity. Still efficient.

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?

Minimal description for a 4-parameter tool with no output schema. Leaves gaps: what is 'adaptive'? What happens if A-record check fails? No mention of return values or effects. Adequate but not comprehensive.

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 coverage is 100%, so description adds no additional parameter-specific meaning. Baseline score of 3 is appropriate as the tool's purpose is clear but parameters rely solely on schema descriptions.

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?

Clear verb ('configures') and specific resource ('Nginx reverse proxy or static web server block'). Includes a prerequisite (domain A-record verification) and distinguishes from sibling tools like configure_firewall or setup_ssl_certbot. Effectively communicates the tool's scope.

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?

Implies usage context (after domain verification) but provides no explicit guidance on when to use vs alternatives. No mention of when-not or other sibling tools. Adequate but lacks depth.

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