tibia_find_items

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

Annotations already establish readOnlyHint=true and openWorldHint=false, so safety is covered. The description does add one genuinely useful behavioral fact beyond the annotations: the tool is currently non-functional because the local index is missing, plus the unmet prerequisite (index must be built). It discloses nothing else about query behavior, limits, or failure modes.

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?

One sentence, front-loaded with 'UNAVAILABLE,' which is the right priority order for an agent. It is not bloated, but it is sparse to the point of under-specification rather than efficient concision.

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 tool with annotations covering safety and no output schema, the description still needs to convey what the tool returns and how it differs from tibia_search/tibia_find_creatures. It delivers only an availability warning and no remediation path or fallback, leaving an agent unable to plan around the failure.

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 and the schema is trivially empty with no descriptions needed, so the baseline of 4 applies. The description neither helps nor harms here, though it also never indicates what input the tool would take once operational.

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 text only reports a runtime status ('index is missing or unusable') and never states what tibia_find_items does when it is available. An agent can infer 'find items' solely from the tool name, and cannot distinguish it from siblings like tibia_search or tibia_find_creatures based on this description.

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 on when to use this tool, and no alternative is offered for the unavailable case even though tibia_search and tibia_get are viable siblings. The only actionable signal is a blanket 'cannot answer anything,' which is effectively a do-not-call notice with no fallback.

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