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

Annotations already declare openWorldHint=true and destructiveHint=false, but the description adds the meaningful consequence: publish=true pushes the card into a public catalog, while dry_run avoids writes. That public-exposure detail is not derivable from the annotation flags. It does not describe idempotency behavior beyond what the request_key schema field states.

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 sentences, front-loaded with the core action and followed by the mode semantics. Slight waste in the vague 'their own project or studio' phrasing, but no padding.

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?

For a six-parameter tool with a nested tool object and no output schema, the description covers the create/preview/publish lifecycle but omits the tool_id-only path for publishing an already-saved tool, which is a distinct mode an agent must know exists from the schema alone.

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%, so every parameter is already documented in the schema. The description merely restates the dry_run/publish semantics at a high level and says nothing about tool_id (publishing an existing saved tool) or project_id beyond the schema.

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?

A concrete verb (save) and a concrete resource (a tool, asset or know-how as a project/studio card) that separates it from generic saving. It does not explicitly contrast with save_project or save_context, so an agent must infer the boundary from the noun alone.

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 conveys the intended sequence - dry_run to preview the card, publish true to place it in the Tavern catalog - which implies when each mode applies. It never names an alternative tool or states when not to use this one over save_project/save_context, leaving routing decisions to inference.

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