models-publish

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

Discloses that publishing lists prior published versions with a hint to archive and allows combined publish-and-archive via archive_version_ids. Without annotations, this adds valuable behavioral context, though it omits details like reversibility or permissions.

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?

Three concise sentences with no fluff: first sentence states primary action, second explains response behavior, third describes combined operation. Front-loaded and efficient.

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?

Covers the main intent, response behavior, and optional parameter usage. Without an output schema, it provides sufficient context for an agent to understand expected outcomes, though it does not detail all response fields.

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 coverage is 100% and the description reinforces the archive parameter's purpose, but adds limited new meaning beyond the schema descriptions. Baseline 3 is appropriate.

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?

Clearly states 'Publishes a Case Plan Model (draft -> published)' with a specific verb and resource, and distinguishes from siblings like models-archive and models-update by specifying the draft-to-published transition and optional archiving of prior versions.

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?

Provides guidance on when to use the archive parameter and describes response behavior with prior_published_versions, but does not explicitly contrast with alternatives or specify when not to use the tool.

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