get_pubsub_status

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

With no annotations, the description carries the burden. It uses 'Debug' and 'show' to indicate a read-only, non-destructive operation. Could be more explicit about safety, but the phrasing adequately implies no side effects.

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?

Extremely concise: one sentence with the action and use case. The word 'Debug' front-loads the intent. Every word earns its place.

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 no parameters and the output is straightforward (channels and subscriber counts), the description provides sufficient context for selection. The lack of output schema is mitigated by the clear description of what the tool shows.

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?

No parameters exist, so schema coverage is 100%. The description adds nothing about parameters, but for zero-parameter tools, a baseline of 4 is appropriate as there are no semantics to clarify.

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?

Clearly states the verb 'show' and the resource 'all active Redis pub/sub channels and subscriber counts'. The purpose is well-distinguished from siblings like 'get_logs' and 'get_version' by focusing on chat sync diagnosis.

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 states when to use: 'Use to diagnose chat sync issues'. While it doesn't mention when not to use or alternatives, the single-purpose context is clear enough for an AI agent.

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