subscribeLiquidation

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

The description lacks any disclosure of behavioral traits such as subscription duration, how to manage subscriptions, or what the output contains. Without annotations, the description should provide safety or side-effect information, but it does not.

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 extremely short (4 characters) but fails to provide necessary context. Conciseness should not sacrifice completeness; here, critical information is missing.

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 complexity (4 parameters, no output schema, many sibling subscription tools), the description is severely incomplete. It does not cover return values, subscription lifecycle, or how to interpret results.

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?

With 0% schema description coverage, the description should explain parameters like symbol, category, etc. It adds no value beyond the parameter names and types, leaving the agent without guidance on required values.

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 'Subscribe to liquidation data' clearly states the verb (subscribe) and resource (liquidation data). It is specific enough to distinguish from many unrelated tools, but it does not differentiate from other subscription tools like subscribeAdlAlert or subscribeExecution.

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 versus alternatives like subscribeAdlAlert or subscribePosition. There is no mention of prerequisites, context, or exclusions.

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