run_site_git_deployment

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

No annotations are provided, so the description carries full burden. While 'Run a git deployment' implies a write/mutation operation, it doesn't disclose critical behavioral traits: whether this triggers a production deployment, what happens to existing site content, if it requires specific permissions, potential downtime, or what the tool returns. For a deployment tool with zero annotation coverage, this is inadequate.

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 a single, efficient sentence that directly states the tool's purpose with zero wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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 the complexity of a deployment operation (potentially destructive), no annotations, no output schema, and incomplete behavioral disclosure, the description is insufficient. It doesn't explain what 'git deployment' entails, the expected outcome, error conditions, or how it fits with sibling tools like cache purging or permission correction.

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?

The input schema has 100% description coverage (site_id is fully documented in the schema), so the baseline is 3. The description doesn't add any parameter-specific meaning beyond what's in the schema—it mentions 'specific WordPress site' which aligns with site_id but provides no additional context about valid IDs or format.

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 action ('Run a git deployment') and the target resource ('for a specific WordPress site'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from potential sibling deployment tools (none are listed in the provided siblings, but the description doesn't explicitly differentiate from general site operations).

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing git configured on the site), when-not-to-use scenarios, or how it relates to other deployment methods. With siblings like 'purge_site_cache' and 'correct_site_file_permissions', some context about workflow ordering would be helpful but is absent.

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