psubscribe

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

With no annotations, the description carries full burden. It states the tool subscribes and returns a dict with subscription ID or error, but does not disclose whether it is blocking, how the subscription lifecycle works, or how to receive messages. This leaves significant behavioral ambiguity.

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 concise and well-structured: a clear one-sentence purpose followed by standard Args and Returns sections. Every sentence adds value with no 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?

For a simple subscription tool with an output schema, the description covers the basics and return value. However, it lacks context on how the subscription integrates with sibling tools (e.g., 'read_messages', 'unsubscribe') and omits behavioral details like blocking semantics, making it only partially 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?

Schema description coverage is 0%, but the description includes an Args section explaining that 'pattern' is a Redis channel pattern to subscribe to. This adds semantic meaning beyond the schema's 'Pattern' label, though it provides no examples of pattern syntax.

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 'Subscribe to Redis channels using a pattern' with a specific verb and resource. It distinguishes from sibling 'subscribe' by emphasizing pattern-based subscription, but does not explicitly name the alternative for exact-channel subscription.

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 usage for pattern-based subscriptions but provides no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives like 'subscribe' for exact channels or how subscription relates to 'read_messages' or 'unsubscribe'.

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