tibia_find_creatures

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered; the description adds genuinely new behavioral information by disclosing the tool's current unusable state and its cause (missing/unusable local index). It stops short of saying what the agent will actually receive on invocation (error vs. empty result) or how to fix the index.

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 sentence, front-loaded with 'UNAVAILABLE' so the critical fact is unmissable. It is appropriately sized for the amount of information it chooses to convey, though it wastes a few words restating the tool name.

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 parameterless, output-schema-less tool the description would normally need little, but here it is the only signal that the tool is out of service and it provides no remediation path, no statement of what the agent will get on a call, and no pointer to the sibling tools that could answer the same question.

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 input schema has zero parameters, which is the baseline-4 case; there are no parameter semantics for the description to explain or 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 only tells the agent the tool is broken; it never states what tibia_find_creatures actually does in a working state (presumably looking up creatures in TibiaWiki). The name carries essentially all of the purpose information, and the text is a status notice rather than a purpose statement.

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 implies the tool should not be called right now ('cannot answer anything until it is built'), which is useful, but it names no alternative even though tibia_search, tibia_get, and tibia_find_items exist as potential fallbacks, and gives no condition under which the tool becomes usable.

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