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

Annotations already cover safety with readOnlyHint, idempotentHint, and destructiveHint=false, so the description only needs to add behavioral context. It does so by noting public pages, ranking relevance to the human, and returning a person's page plus quests to respond to.

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?

It is short and front-loads the main action and trigger. The second sentence is somewhat elliptical, but it still packs useful ranking and return-value hints without 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?

Given six optional parameters, full schema coverage, and no output schema, the description supplies enough context about when to use it, ranking behavior, and the kind of result returned. Minor gaps around pagination and filtering are covered by the schema.

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%, so the parameters are already fully documented structurally. The description only loosely echoes id/link lookup and relevance ordering, adding little parameter meaning beyond the schema.

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 clear verb and resource: browsing the Tavern people catalog, with triggers such as browsing or naming a person. It distinguishes itself from start_quest when a goal exists, though it does not differentiate from other catalog/profile siblings such as search_catalog or profile_card.

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 explicit usage conditions: use when the human wants to browse or names a person, and use start_quest first when there is a goal. It stops short of naming when-not-to-use cases or alternatives like search_catalog.

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