lidarr_add_artist

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

No annotations are provided, so the description must disclose behavioral traits. The description only says 'Add an artist' without mentioning side effects (e.g., whether it triggers a library update, requires authentication, or has rate limits). Missing key behavioral information.

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 one sentence followed by a list of prerequisite tools. It is concise, front-loaded with the main purpose, and every sentence provides essential guidance without 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?

Given the tool has 7 parameters, all fully described in schema, and no output schema, the description provides a solid workflow. However, it lacks information on the return value (e.g., the created artist object) or any post-action behavior. Still, it is complete enough for typical use.

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?

Input schema has 100% description coverage, and each parameter's description adds context beyond the name, such as how to obtain the value (e.g., 'from lidarr_search results'). This helps the agent correctly populate parameters.

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 clearly states the action (add) and the resource (artist to Lidarr). It distinguishes from sibling tools like lidarr_search, which finds artists, and other get- tools that retrieve configuration.

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?

Explicitly tells the agent to use lidarr_search first to obtain foreignArtistId, and lidarr_get_root_folders, lidarr_get_quality_profiles, lidarr_get_metadata_profiles for valid values. Also mentions lidarr_get_tags for optional tag IDs. This provides a clear workflow and prerequisites.

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