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

Annotations declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description usefully discloses the return payload (titles, URLs, summaries, key facts, citation), which matters because no output schema exists, and the local-guides framing is consistent with the closed-world annotation. No contradiction.

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 sentences, front-loaded with the core action and scope, and the parenthetical enumeration earns its length by telling the agent what content exists. The topic list is dense but not padded.

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 read-only search tool with no output schema, the description covers what is searched, the domain scope, and what is returned. Remaining details (limit default of 5, max 10, category filtering) are already in the schema, so nothing an agent needs to call it 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 67%: query and category are documented in the schema itself (including examples and a topic list), while limit has only a default/max. The description adds no meaning beyond the schema for any parameter, so the baseline of 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 specific verb ('Search') and resource ('the hostel's guides') and pins down the corpus with a concrete topic list (CUSAT, NUALS, RCC/CCRC, transport, food, festivals). It does not explicitly distinguish itself from the sibling get_guide, so an agent must infer search-vs-fetch from the names alone.

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 topic enumeration implies when the tool is useful (local questions about colleges, transport, services), but there is no explicit when-to-use statement, no exclusions, and no routing against siblings like get_guide or nearby_places. Usage is only implied.

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