tibia_search

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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false), so the bar is lower. The description adds a genuinely important operational fact not present in annotations: the tool is currently non-functional because the local index is missing. However, it reveals nothing about normal runtime behavior, result format, or limits once the index is available.

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?

A single front-loaded sentence with no padding, and the blocking condition is stated first. The all-caps 'UNAVAILABLE:' prefix reads like a raw error/template artifact rather than authored prose, which slightly undercuts the structure.

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 tool that is part of a five-member TibiaWiki family with no output schema and no parameters, the description should at minimum explain what a successful search returns and how it relates to the find_* and get siblings. Instead it only reports an outage, leaving an agent unable to route to or away from this tool on purpose grounds.

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 tool takes zero parameters, so per the baseline rule a 4 applies. There is no parameter information the description could add or need to compensate for.

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 is a status/failure message rather than a purpose statement: it never says what tibia_search actually searches (TibiaWiki content? pages? entities?) when the index exists. An agent can infer only vaguely from the name that it is a search tool, and there is no differentiation from siblings like tibia_get or tibia_find_creatures beyond that.

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 does convey one implied directive — do not call this until the index is built — which is a usable precondition, but there is no guidance on when this tool is the right choice versus tibia_get or the tibia_find_* siblings, nor any general usage context.

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