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

Annotations already cover the read-only, idempotent, and non-destructive nature. The description adds useful behavioral context beyond that: it returns a summarized projection (slug, name, city) and that the slug is essential for other tools. It does not discuss pagination or limit behavior, but that is minor for this simple read operation.

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?

Two sentences with no filler: the first front-loads the main purpose and return values, the second explains the key parameter. Every phrase adds value, including the note about slugs being needed downstream.

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, read-only listing tool with an output schema and safety annotations, the description is mostly complete. It could improve by mentioning the limit/pagination behavior or explicitly directing agents to get_venue for single-venue details, but these are not critical gaps.

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 description reinforces the query parameter ('Pass query to filter by name or city'), but the schema already documents this. The limit parameter has no semantic description in either the schema or the tool description, leaving its purpose implicit despite having 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 clearly states the tool finds restaurants/venues on Servd and returns a list of slugs, names, and cities. This distinguishes it from singular tools like get_venue, especially by emphasizing the slug as the key needed by every other 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?

The description implies this is the tool to use when you need to discover venues and obtain slugs for downstream calls, saying 'the slug is what every other tool needs.' It gives clear context but does not explicitly state when not to use it or how it differs from get_venue.

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