event_subscribe

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

No annotations provided. The description discloses subscription behavior including permanent subscription via expire=0 and socket format details. However, it does not discuss potential side effects (e.g., resource consumption) or whether subscriptions persist beyond OpenSIPS restart for non-zero TTL.

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 a title line followed by a bulleted list. It is concise and front-loaded, containing only essential information. Minor verbosity in socket format examples could be trimmed.

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 presence of an output schema (not shown) and the complexity of subscription tools, the description covers parameters adequately. It lacks information about return values or errors, but the output schema likely addresses that. Overall, it provides sufficient context for correct invocation.

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?

Despite 0% schema description coverage, the description thoroughly explains all three parameters. It provides concrete examples for event format, socket backend formats (udp, rabbitmq, flatstore), and the special meaning of expire=0. This adds significant value over the bare schema.

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 verb 'Subscribe to' and the resource 'an OpenSIPS event at a given transport socket'. It explains the purpose but does not explicitly distinguish from sibling tools like 'event_list' or 'event_list_subscribers', though the name suggests a write 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 on when to use this tool versus alternatives. The description lacks context about typical use cases, prerequisites, or scenarios where other tools would be more appropriate.

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