subscribe_market_resolution

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

Annotations are absent, so the description must cover behavioral disclosure. It only states that it receives notifications, but does not mention subscription lifecycle, whether a subscription ID is returned, or the need to unsubscribe via unsubscribe_realtime. This leaves important operational behavior undisclosed.

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?

Two short, front-loaded sentences with no filler. The main action and outcome are stated first, and the use case completes it.

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 subscription tool with no output schema or annotations, the agent needs to know how to manage the subscription and what the result looks like. The description omits these details, so it is incomplete for correct invocation and follow-up.

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?

The schema already describes both parameters with 100% coverage. The description adds no extra parameter meaning, so the baseline of 3 applies.

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 uses a specific verb ('subscribe') and resource ('market resolution alerts'), and clarifies that it notifies when markets resolve. It distinguishes itself from sibling subscription tools by focusing on resolution rather than prices or orderbook updates.

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?

It provides a clear use case ('tracking when bets settle and positions can be claimed') that tells an agent when to choose this tool. However, it does not explicitly contrast with alternative subscribe tools or state when not to use it, so some inference remains.

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