validate_production_manifestValidates production metadata manifests by checking required project metadata, production stage, and rights status to confirm readiness before delivery or release.
Checks required project metadata, production stage, and declared rights status. Does not read files, call networks, or publish data.
| Name | Required | Description | Default |
|---|---|---|---|
| manifest | Yes |
Changes observed during successful MCP inspections.
v1.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already establish readOnlyHint=true and destructiveHint=false, and the description adds specific behavioral clarity beyond that: it will not read files, call networks, or publish data. This helps an agent understand the tool's safety envelope and side-effect profile much more concretely.
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 two concise sentences with no wasted words. The core validation purpose is front-loaded, and the clarifying caveats follow naturally without redundancy.
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 what the tool checks and what side effects it avoids, which is sufficient for basic selection. However, with no output schema, it does not explain what the tool returns on success or failure, how validation results are reported, or what 'required' means in practice. These gaps matter for an agent deciding how to interpret the result.
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 schema provides no description for the single 'manifest' parameter, and with 0% schema description coverage the description must compensate. It partially does by explaining that the manifest is checked for required project metadata, production stage, and declared rights status, but it does not specify the expected structure or fields, leaving the parameter semantics somewhat underspecified.
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 identifies a specific verb ('Checks') and a clear resource ('production metadata manifest'), and specifies exactly what is checked: required project metadata, production stage, and declared rights status. This clearly distinguishes the tool's purpose even without sibling comparisons.
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 implies this tool is for validating a production manifest before acting on it, but it does not explicitly state when to use it versus alternatives or what conditions make it the right choice. The 'Does not read files, call networks, or publish data' caveat gives useful exclusionary context but stops short of concrete usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.