club_presence

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

With no annotations provided, the description carries the burden of disclosing behavior. 'See who has been active recently' clearly implies a non-mutating read operation. However, it does not explain what counts as 'active', whether results are ordered/limited, or any authentication or access considerations, leaving some behavioral ambiguity.

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, front-loaded sentence that states the tool's purpose without any wasted words. It is appropriately sized for a simple read tool and every clause 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?

Given the tool's simplicity — one optional, fully-described parameter and no output schema — the description provides enough context for an agent to understand what the tool returns (recently active members). It could define 'active' more precisely or mention default behavior, but the schema covers the window semantics and the overall picture is serviceable.

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 fully documents the single optional 'hours' parameter with type, description, default, and max. The description adds no parameter-specific meaning beyond the schema, so the baseline score of 3 applies. This is acceptable given the schema coverage is 100%.

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 ('See') with a clear resource ('who has been active... in AiTop Club'). It conveys a distinct purpose from sibling tools like club_members, focusing on recent activity rather than the full member roster. It could be slightly more explicit about what fields/format are returned, but the core intent is unambiguous.

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?

There is no guidance about when to use this tool vs alternatives such as club_members or club_heartbeat. The phrase 'active recently' implies a recency-filtered view, but no explicit context, exclusions, or alternative recommendations are provided. An agent would have to infer the appropriate scenario.

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