subscribe_topic

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

No annotations are provided, so the description carries full burden for behavioral disclosure. 'Subscribe' implies a blocking/waiting operation, but the description doesn't state how long it blocks, whether it returns immediately with available messages, or what behavior the timeout/maxMessages parameters trigger. Since it's a messaging operation (not explicitly read-only or destructive), more detail is needed about its runtime semantics.

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?

A single, efficient sentence that states the core action with no fluff. It's appropriately concise given the schema already covers parameter details. The brevity is not a fault in itself, though it could have used the saved space for more behavioral detail.

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 this is a subscription tool with no annotations and no output schema, the description needs to convey more about the blocking behavior, return format, and relationship to batch consumption. The presence of publish_message (opposite) and consume_message (related sibling) in the tool list means the description should differentiate these, but it doesn't. A subscription tool typically has nuanced semantics (blocking, long-polling, delivery guarantees) that are entirely unspecified.

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 100%, so the schema already documents all four parameters (connectionId, topicName, timeout, maxMessages). The description adds no parameter-specific information beyond what the schema provides. Baseline 3 is appropriate since the schema carries the heavy lifting and the description aligns with it.

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 states the verb+resource clearly ('Subscribe to a topic and receive messages'), which is a specific action that distinguishes it from siblings like publish_message and send_message. However, it doesn't explain what happens with the received messages or how they're returned, leaving the core purpose somewhat underspecified for a blocking subscribe 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?

No guidance is provided on when to use this tool vs alternatives. Since there are sibling tools like consume_message, browse_messages, and publish_message, the tool needs to clarify its role (e.g., long-poll subscription versus one-shot consumption) to help the agent choose correctly. No exclusions, prerequisites, or alternative tool references are mentioned.

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