rush_ship_gate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies running a process but doesn't state whether it's read-only, what side effects occur, what 'pre-flight' entails, or what the output represents. This is a significant gap for an agent deciding whether to invoke it.

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 6-word sentence with no fluff or redundant phrasing. It is efficiently front-loaded, but the brevity contributes to vagueness. Still, as far as conciseness alone, it earns its place without waste.

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?

For a 0-param tool with an output schema, the description is the primary source of intent. It fails to explain the '7-vector' concept, what 'pre-flight release readiness' actually means, or when to run this gate. An agent cannot confidently decide to use this tool based on the description alone.

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 tool has zero parameters, so the schema provides no input semantics to document. The baseline for 0 params is 4, and the description appropriately doesn't need to explain parameters. It adds no parameter detail, but none is required.

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 states a specific action ('Run') and a resource ('7-vector pre-flight release readiness cockpit'), but the resource is opaque jargon. It doesn't define what the 7 vectors are or what 'cockpit' means, and it doesn't clearly differentiate from siblings like rush_release or rush_ship_clean. It's not a tautology, but it's vague.

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?

There is no guidance on when to use this tool versus alternatives. No conditions, prerequisites, or exclusions are mentioned. The agent is left to infer that it's related to release readiness, but no concrete selection criteria are provided.

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