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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds only that results are limited to 'open public tasks' (a visibility constraint) and mirrors site behavior; it says nothing about result volume, ranking, or paging beyond what parameters imply.

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 the purpose front-loaded and no filler. The second sentence is compressed to the point of being hard to parse ('a task's qid is start_quest respond_to'), which costs some clarity but not much length.

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 never explains what comes back – item shape, totals, facets, or the paging contract – leaving the agent to infer it from parameter descriptions. It is adequate to trigger the call but thin on how to interpret or iterate results.

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% and each of the 7 parameters already documents its domain, defaults and even the response fields it derives from (data.items[].id, data.next_cursor, data.facets.seek). The description's 'as on the site' framing corroborates but adds no syntax or semantics beyond the schema, so baseline 3 applies.

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?

Specific verb+resource ('Search the Tavern catalog') with the entity types it covers (studios, games, tools, open public tasks) spelled out, and it names siblings it is not (find_people for a person, start_quest for a task qid). The phrasing of the routing sentence is cryptic, but the core identity is unmistakable.

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 gives real routing context: use find_people when you want the owner's person, use start_quest/respond_to when you have a quest qid. That is clear when-to-use-this-vs-sibling guidance, though there is no explicit statement of when a catalog search is inappropriate or what to do when it returns nothing.

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