deployment_readiness

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds meaningful behavioral context beyond that: 'hard blocking for unsafe deployments' and integration with smart_git_push. It does not detail override side effects or the fact that some parameters trigger migrations or health-score updates, but those are visible in the schema.

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 dense sentence that front-loads the tool's purpose, then names three concrete capabilities and one key integration. Every phrase earns its place, and there is no redundancy or vague filler that bloats the definition.

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 tool's complexity — 24 parameters, six operation modes, and no output schema — the description provides a solid summary but leaves operational selection underspecified. It does not explain how to choose among operations like check_readiness, full_audit, or emergency_override, nor how strictMode and thresholds interact with the blocking behavior. The schema describes parameters well, but the description alone would not fully guide an agent through a realistic deployment-readiness scenario.

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 description coverage is 100%, so the schema already documents all 24 parameters thoroughly, including their defaults and enums. The description reinforces themes like test failure tracking and deployment history analysis but does not add parameter-level detail such as when businessJustification is required for emergency_override. The baseline of 3 is appropriate because the schema carries the load.

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 identifies the tool's resource ('deployment readiness') and action ('validation'), while naming concrete capabilities: test failure tracking, deployment history analysis, and hard blocking for unsafe deployments. It also mentions integration with smart_git_push, which helps position it among siblings, though it does not explicitly contrast it with similar tools like analyze_deployment_progress.

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 phrase 'Integrates with smart_git_push for deployment gating' implies the tool is used as part of a pre-deployment safety gate, and the emphasis on 'hard blocking for unsafe deployments' suggests when it should be invoked. However, it does not explicitly state when to use this tool versus alternatives such as release_tracking or analyze_deployment_progress, nor does it mention 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.