opa_get_subscription_events

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

With no annotations provided, the description fully covers behavioral traits: it requires an API key (OILPRICEAPI_KEY), does not count against monthly quota, and explains the polling mechanism. It also discloses that each event carries a price snapshot plus per-code deltas.

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 concise at about 6 sentences, front-loaded with purpose, and each sentence adds valuable context without repetition or fluff.

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 no output schema, the description explains the response structure (events with price snapshot and deltas, cursor for next call), API key requirement, and quota exemption. It is complete for a simple polling tool with one parameter.

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 coverage is 100% for the single parameter 'since'. The description adds meaning by explaining it's a cursor, how to use it from the previous call, and that omitting it or passing 0 gets the earliest events.

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 'Poll for new subscription events' and specifies they are recurring snapshots from user's watches. This distinguishes it from sibling tools like opa_list_subscriptions (listing subscriptions) and opa_create_price_subscription (creating subscriptions).

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?

The description explicitly says to use this to catch up on changes since the last poll and explains how to use the 'since' parameter. It notes that events are polled, not pushed, and should be called periodically. While it does not explicitly state when not to use it, the guidance is clear and sufficient.

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