deploy_site

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

The description mentions that switching targets will trigger a warning to remove old workflow files and implies preference learning. However, it does not detail side effects (e.g., file modifications, commits) or prerequisites like repository analysis, which limits full behavioral 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?

The description is exceptionally concise: two sentences with no wasted words. It front-loads the purpose and critical usage note, making it efficient for an agent to parse.

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?

The description covers the main function and a key constraint but omits details like the need for prior repository analysis (analysisId), behavior of preference learning, and what the tool outputs. Given no output schema, these gaps reduce completeness.

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?

With 80% schema description coverage, most parameters are explained in the schema. The description adds value only by elaborating on 'target' usage. Baseline 3 is appropriate as the schema does the heavy lifting.

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 tool sets up deployment workflows for GitHub Pages or Vercel, with tracking and preference learning. It specifies the resource (deployment workflow) and actions (setup, track, learn). This distinguishes it from sibling tools like deploy_pages, which likely handles only the deployment 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?

The description explains the use of the 'target' parameter and warns about switching targets. However, it does not provide guidance on when to use this tool versus alternatives like deploy_pages or verify_deployment, leaving the agent to infer context.

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