homestead_install

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

With no annotations, the description fully carries the burden. It discloses that the tool returns immediately with a job id, that work takes minutes, and that the first index build downloads a ~2 GB embedding model – all critical operational details. This is exemplary transparency.

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?

Three sentences with no waste: purpose is front-loaded, async behavior and polling follow, and the model download is mentioned last. Every sentence adds value.

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?

Fully adequate for a complex tool. It covers purpose, usage, async workflow, and a significant resource warning (2 GB download). It also states the return value (job id) despite no output schema. Nothing an agent needs to call it correctly is missing.

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 parameters are already documented. The description adds a useful pointer to homestead_catalog for shelf slugs but doesn't elaborate on pack or index beyond the schema. Baseline 3 is appropriate since the schema handles parameter documentation.

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?

States a specific action (download and index documents) and resource (library), and clarifies its role as the initial setup tool ('set a library up from nothing'). This distinguishes it from sibling tools like homestead_add, which likely handle incremental additions.

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 explicit guidance on when to use it (setting up a library from nothing) and how to handle the async job (poll homestead_job until done). It doesn't explicitly name alternatives like homestead_add, but the context strongly implies it's for initial bulk setup rather than ongoing additions.

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