Search for board games in our catalog to find their BoardGameGeek IDs (required for filtering events by game).
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Name of the board game to search for | |
| limit | No | Maximum number of results to return |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the burden. The verb 'Search' implies a non-mutating read operation, which is the primary behavior. However, the description does not explicitly state that it is read-only or safe, nor does it mention any output format beyond the implicit BGG ID.
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 that front-loads the action ('Search') and the resource. No unnecessary words are present.
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 low complexity (2 parameters, no output schema, no annotations), the description is adequate. It states the tool's purpose and the reason for using it (to get BGG IDs for filtering events). The schema covers parameter semantics, so the description doesn't need to repeat them. However, it could be slightly more explicit about the return format.
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% for both parameters (q and limit), so the baseline is 3. The description adds the context that q is the game name used to find BGG IDs, but it does not provide additional details about the limit parameter or any constraints.
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 the specific verb 'Search' with the resource 'board games in our catalog' and states the purpose: to find BoardGameGeek IDs. This clearly distinguishes the tool from sibling search tools like search_events and search_venues.
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 explicitly mentions that the tool is 'required for filtering events by game', which clarifies the primary use case. However, it does not explicitly mention alternatives or exclusions, though the purpose makes it self-evident.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool targets a distinct resource and action: user registration, event creation, RSVP, and separate searches for events, games, and venues. There is no overlap in purpose, so an agent can easily select the right tool.
All tool names follow the verb_noun pattern (create_event, register_user, rsvp_event, search_events, search_games, search_venues). Even 'rsvp_event' uses a verb-like acronym consistently, and the snake_case style is uniform.
Six tools is well within the ideal 3-15 range for a focused domain. Each tool has a clear role, and there are no redundant or excessive entries.
The toolset covers the main workflows: searching for venues/games/events, creating events, RSVPing, and registering users. Minor gaps exist such as no cancel_rsvp or update_event, but these are not core dead ends and agents can work around them.
