KBK Live Stats

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

With no annotations, the description carries the burden. It indicates 'live' data and 'aura in the last 24h', implying real-time snapshot and a time window, but it doesn't explicitly state that the operation is read-only or non-mutating, nor does it mention any rate limits or caching behavior. The term 'stats' suggests safety, but that is implied rather than 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 a single sentence, front-loaded with 'Live platform stats' and enumerates the metrics compactly. It avoids unnecessary phrases, though the list is somewhat long and could benefit from formatting, but overall it is efficient and earns its place.

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 parameterless tool with no output schema, the description adequately conveys the type of data returned. It lists all major stat categories, including time-bound data (aura in last 24h) and uptime. It could specify the return structure (e.g., a single object), but the coverage is sufficient for this simplicity level.

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 tool has zero parameters, so schema coverage is 100% and the baseline is 4. The description does not need to explain parameters, and it instead lists the returned metrics, which is appropriate for a parameterless stats endpoint.

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 states the tool provides 'Live platform stats' and lists seven specific metrics (wolves online, tracks spun, average BPM, etc.), making the purpose unambiguous and differentiating it from sibling tools like get_twitch_status or get_live_alert which target narrower domains. The verb 'stats' is implicit but the resource is clearly the platform's live overview.

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 implies use when an agent needs overall platform statistics, but it does not explicitly state when to use it over alternatives or exclude cases (e.g., if you need track-specific details, use get_track or search_tracks). No contextual guidance beyond the basic stats listing is provided.

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