list_settings_plex_library

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

The description explicitly says 'sync' syncs libraries and 'enable' can disable any libraries not passed, which is mutation and potentially destructive. This directly contradicts the annotations readOnlyHint=true and destructiveHint=false, making the tool's behavior dangerously ambiguous despite the description's detail.

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 brief and front-loaded with the core purpose, followed by a clean endpoint line and two parameter bullets. Every line earns its place, though the sync value format could have been clarified without much extra length.

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?

The output schema exists, so return values need not be explained, but the tool's behavior is incomplete: it does not clarify valid sync values, combination semantics with enable, or the relationship to list_settings_plex_sync. The annotation contradiction on mutability further undermines completeness.

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 0%, so the description must explain the parameters. It does partially: 'sync' is described as syncing with the Plex server, and 'enable' is explained as a comma-separated list with a clear disable warning. However, sync's accepted value format and how the parameters interact are left unclear.

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 'Get Plex libraries' and gives the exact endpoint, so the verb and resource are clear. It does not distinguish itself from siblings like list_settings_plex or list_settings_plex_sync, but the resource is specific enough that an agent can identify the intended operation.

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?

There is no guidance on when to call this tool versus the closely related sibling list_settings_plex_sync or list_settings_plex. The description only lists parameters; it never states when this endpoint is the right choice or when an alternative should be used.

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