get_series_folder

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

No annotations are provided, so the description carries the full burden. It clearly indicates this is a read-style computation ('would use') dependent on 'current naming configuration,' which implies no state mutation. It does not cover edge cases like behavior for invalid series IDs or whether the returned path is absolute.

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, front-loaded sentence with no filler. The verb, resource, and condition are all immediately clear, and 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 one-parameter getter with no output schema, the description adequately conveys what is returned and what it depends on. It is complete enough for correct invocation, though it could optionally mention whether the series must already exist or how the path is formatted.

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 input schema already documents id as 'Sonarr series id' with 100% coverage. The description adds context that the id selects the series whose folder path is computed, but it does not add meaning beyond what the schema provides.

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 a specific operation: retrieving the folder path Sonarr would compute for a series under the current naming configuration. This is distinct from siblings like get_series and get_naming_config, though it does not explicitly call out alternatives.

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 you need to know where a series' files would be placed based on current naming settings. However, it does not explicitly state when to prefer this over related tools or mention any prerequisites such as the series already existing.

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