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

The annotations already establish that this is a read-only, idempotent, open-world, non-destructive tool. The description adds useful behavioral context beyond that: current listings from a specific site, a 20-result cap with no paging, result links pointing to bise.ws pages where details are confirmed, and refusal reasons being returned.

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 front-loaded with the geographic and site scope, then moves through inputs and result behavior. It is somewhat dense and repeats a few schema details such as the 20-result cap and date behavior, but the Turkish search keywords and refusal behavior are useful rather than filler.

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 7-parameter search tool with no output schema, the description covers the essential constraints, filtering guidance, result cap, link format, and refusal behavior. It does not fully describe the shape of each returned event record, but it gives enough for correct invocation and interpretation of result links.

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%, so the baseline is 3. The description adds meaningful semantics not encoded in the schema's required fields: at least one of city, category, or q must be supplied even though no parameter is formally required. It also reinforces that district filtering depends on city and that dates or words make results more specific.

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 a specific verb and resource: it searches current event listings on biseyvarmi.com, scoped to Türkiye only. It enumerates event types, cities, districts, dates, venues, and prices, so an agent can immediately tell this is a Turkish event search tool rather than a generic search or fetch tool.

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?

It gives clear usage conditions: at least one of city, category, or q is required, results are capped at 20 with no paging, and district/category/date/word filters make results more specific. It does not explicitly compare against the sibling tools `search` and `fetch`, so it falls short of full alternative routing guidance.

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