MiSTerClaw

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

With no annotations, the description carries the full burden. It adds valuable behavioral context: setup 'returns auth URL if needed', start/stop control a daemon, and the VPN enables remote access. However, lacks details on error conditions, idempotency, network requirements, or persistence.

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?

Efficient two-sentence structure front-loaded with purpose. First sentence covers management scope and action summaries; second explains Tailscale's value. No redundant fluff, though the value proposition sentence could be considered slightly generic.

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?

Appropriately complete for a multi-action tool without output schema. Covers all four action variants and mentions key return values (auth URL for setup, IP for status). Could strengthen with workflow sequencing (setup → start) but covers the essentials well.

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 has 100% description coverage (both action and hostname fully documented). The description aligns with the schema but does not add significant semantic depth beyond what the schema already provides (e.g., hostname format examples, default behaviors). Baseline 3 is appropriate for high-coverage schemas.

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 specific verb ('Manage') + resource ('Tailscale VPN') + scope ('MiSTer-FPGA'). Explicitly distinguishes from sibling mister_* tools (none others handle VPNs) by stating the specific domain.

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?

Provides clear context by explaining what each of the four actions does (setup configures, status shows IP, etc.), serving as implicit guidance. Lacks explicit prerequisites (e.g., 'setup must run first') or 'when not to use' exclusions, preventing a 5.

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