tibia_how_to_obtain

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

Annotations declare a safe read-only, non-open-world operation, and the description adds a critical fact those annotations do not carry: the tool is currently non-functional. However it does not say what a call actually returns in this state (error, empty result, or refusal), so the failure mode remains unspecified.

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 that front-loads the 'UNAVAILABLE' status, which is the most important thing an agent needs to know. No wasted words, though the sentence is really a status banner rather than a tool definition.

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 zero-parameter, read-only tool with no output schema, the description is adequate in flagging that it cannot answer anything. It is incomplete in that it offers no remediation path or statement of what the tool would do once the index exists, leaving the agent unable to plan around it.

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 there is no parameter semantics to convey; the baseline of 4 applies. The empty schema is consistent with the description.

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 never states what tibia_how_to_obtain actually does when operational; it only reports that the backing TibiaWiki index is missing. The agent must infer the function (explaining how an item/spell is acquired) entirely from the name, and there is no differentiation from siblings like tibia_find_items or tibia_get.

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?

There is no guidance about when to use this tool versus the sibling lookups, nor any redirect to an alternative while the index is down. The only implicit message is 'do not call this,' which is a status notice rather than usage guidance.

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