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

With no annotations, the description carries the full burden of behavioral disclosure. It reveals an important fallback behavior (use session.city) that is not obvious from the schema. However, it does not disclose whether the operation is read-only or any other side effects, leaving room for uncertainty.

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?

The description is two sentences, front-loaded with the primary purpose, and every word earns its place. No fluff; the fallback instruction is a necessary addition.

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?

The description covers the main search intent and the fallback, and an output schema exists so return values are handled. However, it leaves gaps such as the semantics of 'limit' and behavior when session.city is unavailable. For a simple search tool, it is adequate but not fully complete.

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 0%, so the description must compensate. It only clarifies the 'city' parameter's optionality and fallback, but provides no additional meaning for 'limit' (the default 3 is not explained) or 'session_id' (required but not contextualized). The description helps with one of three 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 the action ('Search'), the resource ('homestays'), and the scope ('in a city'), clearly distinguishing it from sibling tools like search_hotels and search_activities_in_city. It is specific and unambiguous.

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 a clear contextual instruction: if city is omitted, use session.city from a prior hotel search. This helps the agent know when the tool can be used and how the city parameter is derived. However, it does not explicitly mention alternatives or exclusions, so it is not a 5.

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