betr_statwars_events

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

With no annotations provided, the description carries the full burden. It only states that it returns data without disclosing behavioral traits such as cache freshness, rate limits, authentication, or whether data is real-time. The read-only nature is implied but not explicitly stated.

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 very short (two lines), which is good for conciseness, but the first line is somewhat vague ('Statwars master events (head-to-head stats promo events)') and the return format is given in code-like notation. It could be more precise while remaining 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?

Given the tool has no parameters and no output schema, the description adequately lists the return fields. However, it does not explain what 'Statwars' means or how these events relate to other betr tools, leaving some domain-specific context missing for an agent unfamiliar with the platform.

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?

There are no parameters, and the schema is empty (100% coverage). The description adds value by listing the return fields (EventTypeId, EventTypeDesc, MasterEventId, MasterEventName, MinAdvertisedStart), which the schema does not specify. This provides meaningful context for the agent.

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 that the tool returns 'Statwars master events (head-to-head stats promo events)' and provides the return structure. It distinguishes itself from sibling tools by name (betr_statwars_events is unique), but does not explicitly differentiate from similar tools like betr_promotions or betr_master_event.

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 betr_promotions or betr_event_types. There is no mention of context, prerequisites, or when not to use it.

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