waiaas

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only indicates this is a read operation ('Get') but fails to mention pagination, rate limits, authentication requirements, return format, or whether the category filter accepts arbitrary strings or specific enumerated values.

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?

Single efficient sentence with zero waste. The parenthetical clarification earns its place by providing crucial domain-specific context without verbosity.

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?

Adequate for a simple single-parameter tool, but lacks important operational context expected when annotations are absent—specifically available category values, return structure, or pagination behavior.

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% with the 'category' parameter already described as 'Event category filter.' The description adds no additional parameter syntax or semantics beyond the schema, which is acceptable given the baseline of 3 for high schema coverage.

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 provides a specific verb ('Get') and resource ('Polymarket events'), plus the parenthetical clarification '(groups of related markets)' effectively distinguishes this from the sibling tool `waiaas_pm_get_markets` by defining the conceptual relationship between events and markets.

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 defines what events are but provides no explicit guidance on when to use this tool versus siblings like `waiaas_pm_get_markets` or `waiaas_pm_get_market_detail`, nor does it mention prerequisites or filtering strategies.

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