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

The readOnlyHint annotation already covers the safe read-only nature of the tool. The description adds one useful behavioral signal by implying that detailed spell properties are not included here and must be fetched via tibia_get, but it does not mention pagination, default limits, or inactive-spell filtering.

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?

Two compact sentences with no filler. The main purpose is front-loaded, followed by a concrete example and a pointer to the sibling tool, all in minimal space.

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?

With 10 filter parameters and an output schema present, the description gives enough for basic use but omits guidance on pagination and several boolean/optional filters. It is adequate for a simple search query but not fully complete for advanced filtering.

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 only 40%, and the description does not compensate for the gap. It lists filter dimensions like 'vocation, level, group, element and type' without mapping them to actual parameter names, and it omits meaning for cursor, limit, is_premium, include_inactive, and spell_type, which are otherwise undocumented except for their enums.

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 opens with a specific verb and resource, 'Find Tibia spells by vocation, level, group, element and type', making the tool's function immediately clear. It also distinguishes itself from sibling find_* tools by naming the exact resource and gives a concrete example query.

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?

'Use this for questions like...' explicitly states the intended use case. It also names the relevant alternative, tibia_get, and defines the boundary: use tibia_get for cooldowns, effect, and area. This is clear routing guidance.

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