create_alias

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

No annotations are provided, so the description carries the full behavioral burden. It clearly discloses that creating the alias changes how Medusa handles future searches, and adds the important scope limitation that only local, user-managed exceptions can be created. This goes beyond a bare 'create' statement and gives the agent a solid mental model of effects.

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?

The description is compact: a short lead sentence stating the operation and a two-sentence expansion explaining purpose and scope. It is front-loaded with the most important information and contains no irrelevant enfluff or abstruse.

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 simple creation tool with an output schema and 100% parameter coverage, the rest of description addresses what the operation does, why it is needed, and its local scope. The only missing detail is duplication behavior (what happens if the same alias again), but that's not essential for calling the tool successfully.

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 the baseline is appropriate. The description does not define the individual parameters but does contextualize 'name' as an 'alternative release title', which is a minor clarification over the schema text (which says 'The alternative title to add as a scene exception'). No additional parameter-level information is provided.

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 opens with the specific verb-resource pair 'Create a local scene exception (alias) for a series' and then explains the operational purpose: enabling Medusa to recognize alternative release titles. It is clearly distinct from siblings like delete_alias and get_aliases, and the local-scope caveat sharpens the definition.

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 implies when to use the tool: when a series needs a locally-managed alternative title for search matching. However, it does not explicitly contrast with sibling tools such as get_aliases or delete_alias, and the 'Only local' note hints at alternatives without naming them.

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