publish_app

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

The description explicitly labels the tool as 'Destructive' and explains the confirm flag's role in executing vs. previewing. Since no annotations are provided, the description carries the full burden, and it does so well by warning about the destructive nature and the need for confirmation. It could add more detail about irreversible consequences, but it covers the key behavioral trait.

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 sentences, front-loaded with the primary purpose, and every word earns its place. It efficiently conveys the destructive nature, the confirm flag's function, and the preview behavior without any fluff.

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 (destructive action, confirmation flag, preview mode) and the lack of annotations or output schema, the description is quite complete. It explains the critical behavior (preview vs. execution) and the required confirmation. It could mention what happens after publication (e.g., build status) but that is not essential for safe invocation.

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 already provides 100% coverage with descriptions for all three parameters. The description adds context about the 'confirm' parameter's role in execution vs. preview, which is valuable, but it doesn't add much beyond what the schema already states. The baseline for high schema coverage is 3, and the description meets that without significantly exceeding it.

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's purpose: 'Starts publication to the chosen stores.' It uses a specific verb ('Starts publication') and resource ('chosen stores'), and distinguishes itself from siblings like 'unpublish_app' and 'preview_app' by explicitly mentioning the destructive nature and the preview behavior.

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 explicit usage guidance: it states that calling without 'confirm:true' returns a preview and performs no write, and implies that to actually publish, one must set 'confirm:true'. This clearly differentiates the execution mode from the preview mode, which is essential for safe usage.

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