plex_help

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

Annotations provide readOnlyHint=true, and the description adds valuable behavioral context: it specifies the return format (success, operation, tools, help, error) and provides usage examples. There is no contradiction with annotations.

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 well-structured with headings and sections (operations, return format, examples), making it easy to scan. The 'PORTMANTEAU PATTERN RATIONALE' section is slightly verbose but explains why multiple operations are consolidated, which is useful for the agent. Overall, every section serves a purpose.

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?

With no output schema, the description provides a comprehensive return format and usage examples. All 5 operations are described, parameters are covered through the operation list and examples, making it complete for a help tool of moderate complexity.

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% and the description adds depth beyond the schema: each operation enum value is explained in the OPERATIONS section, and examples clarify how tool_name relates to tool_info/examples. This goes beyond the schema's minimal descriptions.

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 is a 'Comprehensive help and discovery tool for PlexMCP' and enumerates five specific operations (help, list_tools, tool_info, examples, api_docs). This distinguishes it from sibling tools that focus on specific media operations.

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 mentions it facilitates 'autonomous exploration of available capabilities without requiring external documentation', giving clear context for when to use it. However, it does not explicitly name alternatives or state when *not* to use the tool, though that is reasonably implied for a help tool.

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