plex_performance

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

The description lists `delete_profile` as an operation, which is destructive, but the annotations declare `destructiveHint: false`. This is a direct contradiction, so by rule, behavioral transparency scores 1.

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 structured with clear sections (rationale, operations, return format, examples) and is appropriately sized for a multi-operation tool. Every section serves a purpose, though it is lengthy.

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?

Despite the annotation contradiction, the description covers a broad set of operations, provides a generic return format, and shows usage examples. It lacks explicit parameter-to-operation mapping, but the schema covers parameter definitions, making the description reasonably complete.

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 describes all 10 parameters with high coverage. The description adds value by including concrete usage examples (e.g., `set_quality` with `profile_name` and `quality`), which illustrates how parameters map to operations beyond the schema's individual definitions.

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 tool's scope as 'Comprehensive performance, quality, and server status operations for Plex Media Server' and enumerates 12 specific operations with actionable verbs (get, set, create, delete). This distinguishes it from sibling tools by consolidating multiple domains into one interface.

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 portmanteau rationale explains that the tool consolidates transcoding settings, bandwidth monitoring, and server health, implying it's the central place for these operations. However, it doesn't explicitly compare against sibling tools or specify when not to use it, leaving some inference to the agent.

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