unlock_search

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

No annotations are provided, so the description must disclose behavioral traits, but it only says 'search for unlock events with filters'—adding little beyond the tool name. It does not indicate the read-only nature, response format, filter combination logic, or any limitations.

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, clear sentence with no fluff, front-loading the key action and resource. It is concise, though it sacrifices valuable context by being so brief.

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 search tool with six optional filters and no annotations or output schema, this description is severely incomplete. It does not explain what unlock events are, how filters interact, what the response looks like, or how it differs from unlock_get_upcoming and unlock_get_calendar.

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 description coverage is 100% since each parameter has a 'Filter by X' description, so the baseline score of 3 applies. The tool description itself adds no parameter details beyond what the schema already provides.

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 the tool searches for unlock events, using the verb 'search' and specifying the resource 'unlock events'. However, it does not differentiate this tool from sibling tools like unlock_get_upcoming or unlock_get_calendar, which also deal with unlock events.

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 provides no guidance on when to use this tool versus the many other unlock-related tools. It does not mention alternatives, exclusions, or typical use cases, leaving the agent without context for selection.

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