Run a saved skill

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false; the description adds that it dispatches a generation job and that it blocks waiting for the result by default, which is meaningful for latency-sensitive callers. It does not mention cost/credit consumption or what happens on template/variable mismatch, which keeps it below a 5.

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 the core action first and the mechanics after, plus one short sentence on the default wait behavior. No filler.

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?

With full schema coverage, an output schema, and annotations, the description covers what an agent needs to invoke correctly. The minor gap is that it does not state the cost/credit implications of dispatching a generation job or the error surface for missing variables.

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%, so the schema already documents skillId, variables, overrides, and wait. The description restates the same semantics (variables -> template tokens, overrides -> merged over defaults) rather than adding format or validation detail, so the baseline 3 applies.

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 and resource ("Run a saved skill") and then enumerates the three concrete operations it performs: rendering the prompt template with variables, merging overrides over defaults, and dispatching a generation job. This is clearly distinguishable from siblings like create_skill, update_skill, delete_skill, and get_skill.

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 only implied: the description conveys that this is the execution step for a saved skill, but never says when to prefer it (e.g., after create_skill or get_skill), nor mentions prerequisites such as obtaining skillId from list_skills. No exclusions or alternatives are named.

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