abs_podcasts

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

Despite annotations already declaring destructiveHint=true and readOnlyHint=false, the description goes further: it names the auth mechanism (Bearer ABS_API_TOKEN), the environment gate (ABS_ALLOW_WRITES=true), the dry-run-by-default behavior ('sends nothing'), and the specific set of actions that trigger extra warnings (delete, scan, match, purge, backup restore, user changes, API key create/revoke, password, settings). This is the kind of safety context annotations cannot convey.

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?

Purpose is front-loaded in the first clause, followed by auth, write protocol, and the action inventory. Nothing is padded, though the confirm/dry-run explanation duplicates the schema's own description, a minor redundancy.

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 6-parameter action dispatcher with no output schema, the description covers auth, write gating, dry-run behavior, destructive-action warnings, and per-action help discovery. The main remaining gap is that the return shape is undocumented, which matters here since no output schema exists to compensate.

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 baseline is 3. The description restates the confirm semantics that the schema already documents verbatim and doesn't add structure for body/query/params beyond what the schema says. The only marginal addition is the ABS_ALLOW_WRITES prerequisite, which is environmental rather than parameter-level.

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 names the resource ('podcasts toolset' in Audiobookshelf) and enumerates all 12 actions, so the agent can tell it apart from siblings like abs_items, abs_series, or abs_playlists. The framing verb ('covers the podcasts toolset') is generic, but the action list supplies the concrete specificity.

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?

It states the environment constraint ('self-hosted Audiobookshelf only'), points the agent to 'action help with target' for per-action parameter discovery, and spells out the write path (confirm=true plus ABS_ALLOW_WRITES=true) versus the dry-run default. It doesn't explicitly say when podcast tasks should route here instead of a sibling, but the resource scoping makes that largely self-evident.

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