deploy_honeypot

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

No annotations provided. The description calls it 'ephemeral' but does not detail lifecycle behavior, such as what happens on deployment (e.g., resource creation, IP exposure), how auto-destruction works, or any side effects on the system. An agent would not know what happens beyond deployment.

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, no fluff. Perfectly concise for conveying the core purpose.

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 output schema and no annotations, the description is too minimal. It does not explain the deployment output (e.g., how to access the honeypot, status), how to clean up (though destroy_honeypot exists), or how the server interacts with other tools. The tool deploys a resource, but the description lacks operational context.

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 the schema already documents all 4 parameters adequately. The description adds no extra meaning beyond what the schema provides. For example, 'template' enum values are self-explanatory from the schema.

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 verb 'Deploy', the resource 'an ephemeral decoy MCP server', and the purpose 'to detect adversarial probing'. It distinguishes itself from siblings like destroy_honeypot and list_honeypots.

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?

No guidance on when to use this tool versus other security tools (e.g., scan_security, run_incident_playbook). No mention of prerequisites, such as required permissions or network setup. The description does not indicate when not to use it.

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