publish_partial

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

Discloses that it immediately changes the default for all prompts, replaces the active version, and has no rollback path. This adds value beyond annotations (which indicate non-read-only behavior).

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?

Two concise sentences: first states purpose and differentiation, second gives usage guidance and consequences. No redundant information.

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 simple two-param schema, annotations, and presence of an output schema, the description covers purpose, usage, effect, and caution. Sufficient for correct tool 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?

Schema covers 100% of parameters with descriptions. The description provides usage context (e.g., 'use after list_partial_versions') but adds no new meaning to the parameters themselves.

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 publishes a specific partial version as default and distinguishes it from update_prompt_partial, which creates a draft. It specifies the effect on partial resolution.

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?

Explicitly advises to use after list_partial_versions to pick a version_id, describes immediate changes and no rollback path. Lacks explicit 'when not to use', but context is sufficient.

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