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

Annotations already declare readOnlyHint=false, idempotentHint=false and destructiveHint=false, so safety is largely covered; the description adds genuinely new context by stating that the published version is immutable and singular, which explains why non-idempotent publishing creates a new version rather than mutating an existing one. It does not add auth or error behavior beyond what the schema's apiKey description already provides.

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?

A single front-loaded sentence with no filler; 'immutable' and 'readiness-checked' carry the two most decision-relevant constraints at the front.

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?

Annotations cover the safety profile and there is no output schema to explain, but the tool takes a nested, fully open manifest object and the description gives no hint of its expected contents or whether a version identifier is returned. For a publish/versioning operation that gap is noticeable, though not crippling.

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%: both apiKey (with pattern and sensitivity note) and manifest are documented in the schema itself. The description adds no syntax, format, or content guidance for the manifest object, whose structure is left as an open-ended additionalProperties object, so it stays at the 3 baseline.

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?

States a specific verb (publish) plus the resource and unit of work (one immutable, readiness-checked agent manifest version), which sets it apart from the read-oriented siblings like check_agent_readiness and get_mission. It stops short of explicitly naming which sibling to use instead when the agent only wants to verify readiness or fetch a manifest.

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?

Usage is implied by the word 'readiness-checked', suggesting a readiness precondition before publishing, but nothing states when to publish versus when to run check_agent_readiness first, nor what happens if the manifest is not ready. The agent must infer the workflow ordering.

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