subscribe_to_show

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does this well by explicitly stating that the tool previews a deterministic PLAN by default and only changes anything when dry_run=false. For a mutation-capable tool, this boundary between read-only preview and side-effecting commit is exactly the behavioral context an agent needs. It could also mention idempotency or partial-failure behavior, but the current disclosure is strong.

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 a single sentence, front-loaded with the action, and immediately provides the crucial default-safe behavior. There is no filler, and the inclusion of the endpoint in parentheses is a useful compact addition. Every word earns its place.

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 3-parameter tool with 100% schema coverage and no output schema, the description covers the necessary invocation context: what it does, the endpoint, the default plan preview, and how to commit. It does not enumerate edge cases like duplicate show IDs, invalid IDs, or partial failures, but those are not essential for an agent to invoke the tool correctly. The description is sufficiently complete for its complexity.

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?

The schema description coverage is 100%, so all three parameters (show_ids, dry_run, response_format) are already fully documented in the schema. The description adds value by tying dry_run to the PLAN-vs-commit semantics, which reinforces the schema's own dry_run text. This is a reasonable baseline-3 case: the schema does the heavy lifting and the description adds a small but meaningful behavioral clarification.

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 a specific verb and resource: 'Save one or more shows to your library', and even includes the underlying endpoint (PUT /me/shows). This clearly distinguishes it from sibling tools like unsubscribe_from_show or remove_saved_shows, despite the large sibling list. The action and scope are completely unambiguous.

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 provides clear guidance on the dry_run default: preview the deterministic PLAN by default, and pass dry_run=false to actually commit. This tells an agent when it is safe to call and what flag flips it into a mutating mode. It does not name alternative tools for similar operations, but for this tool the primary usage decision is the dry-run versus commit choice, which is explicitly covered.

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