Find place or room code

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds output-interpretation context the annotations cannot: cities return an undated listing count and a province `listings` value is not a search count, warning the agent about a plausible misuse.

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?

Front-loads the core transformation and stays compact, with the reverse-mapping note and the 'Next:' routing fragment kept brief. It is slightly dense with backtick-quoted field references and the trailing routing clause is a touch clipped, but no sentence is wasted.

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?

An output schema exists, so return structure needn't be described, and the description still adds what matters: what the input maps to, the interpretation caveat on counts, and where to go next. Nothing an agent needs to call this 1-parameter lookup correctly is missing.

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 100% and the single `query` parameter already documents accepted forms (Persian name, English slug, numeric room code) with examples. The description restates the same duality without adding format, length, or validation detail beyond the schema, so baseline 3 is appropriate.

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?

States a concrete transformation: a place name becomes city/province slugs for ot_search_rooms, or a room code becomes its room. It names the exact input/output resources and clearly separates this from sibling lookups, so an agent can identify the tool without opening the schema.

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?

Explicitly states the exclusion ('Room names are not searchable here') and redirects to the correct alternative with the parameter to use ('use ot_search_rooms with `name`'). It also routes downstream consumers ('Next: ot_search_rooms, or ot_room for a room hit'), leaving no ambiguity about when this tool applies.

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