ws_get_updates

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

With no annotations, the description carries the full burden. It indicates a read operation ('Get') but doesn't disclose whether it requires an active subscription, what happens when there are no updates, whether it's a polling vs streaming endpoint, or what the response format is. Minimal behavioral disclosure.

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 a single, concise sentence with no wasted words. It's appropriately sized for a simple tool, though it could be slightly more informative while still being concise.

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 simple one-parameter tool, the description is sparse. It lacks context about the subscription lifecycle, what kind of updates are returned, and how this tool fits with ws_subscribe_* and ws_list_subscriptions. Given no output schema or annotations, the description is insufficient.

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 provides 100% description coverage for the only parameter (subscriptionId with 'Subscription ID returned from subscribe call'). The description adds nothing beyond that, but since the schema is fully documented, baseline 3 is appropriate.

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 'Get' and resource 'latest updates for a subscription', clearly indicating it retrieves update data for a given subscription. It doesn't explicitly distinguish from sibling subscription management tools (e.g., ws_list_subscriptions, ws_subscribe_*), but the name and phrasing make the purpose reasonably clear.

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 provides no guidance on when to use this tool versus alternatives, no prerequisites (e.g., need an active subscription from ws_subscribe_*), and no context about how updates are produced. It merely states the function without explaining usage scenarios.

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