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

The description discloses important search behavior beyond the readOnlyHint annotation: case-insensitive ASCII matching, the fields searched (title, name, summary, change list), newest-first ordering, and that it returns matching change lines. This is exactly the behavioral context an agent needs.

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?

Three dense sentences cover purpose, examples, matching behavior, ordering, return content, and the follow-up call to tibia_get. Information is front-loaded and there is no filler.

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?

Given the output schema and parameter documentation, the description is complete enough for an agent to correctly select and invoke the tool. It covers what is matched, how results are ordered, what is returned, and how to retrieve full changes.

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 description adds useful meaning for the text parameter by explaining where and how matching occurs, and it summarizes release-date filtering. The schema already documents text, released_after, and released_before, so the description does not need to repeat those details; limit and cursor are left as standard pagination parameters.

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 states a specific verb and resource: 'Find Tibia game updates by text and release date.' The examples like 'what changed for knights in 2026' make the intended use unmistakable, and the resource name clearly distinguishes it from sibling tools like tibia_find_creatures, tibia_find_items, and 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?

The description gives explicit use cases and a clear handoff: 'For the full changes, call tibia_get with type "update" and the returned title.' This tells an agent when this tool is appropriate and when to switch to an alternative.

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