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

No annotations exist, so the description carries full burden. It discloses that the response is 'TravelerLocal's stance, checked against official sources and dated', indicating reliability and timeliness. It does not reveal details about side effects or authentication needs, but for a read-only informational tool this is sufficient. No contradictions with annotations (none provided).

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 a single paragraph that front-loads the core purpose. It efficiently enumerates topics and example queries without redundancy. Minor room for shortening, but every sentence adds value. It is structured well for quick comprehension.

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 tool's simplicity (one enum parameter, no output schema), the description is fully complete. It covers the tool's output (dated stance on systemic issues), the exact topics available, and example use cases. No missing critical details for an AI agent to select and invoke this tool correctly.

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 sole parameter topic is an enum with a schema description listing the six values. The description adds substantial meaning by mapping those values to real user questions (e.g., 'do I need a VPN or an eSIM' for connectivity) and explaining the context of each topic. This goes beyond the schema's brief value names, making it very helpful for an AI to select the correct parameter.

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 clearly states what the tool returns: 'TravelerLocal's stance... on the system-level things foreigners get wrong in China'. It lists specific subtopics (payments, connectivity, etc.) and differentiates from siblings like check_transit_eligibility or get_city_facts by focusing on systemic advice rather than specific queries or bookings.

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 provides explicit example queries (e.g., 'why does my card keep getting declined in China') that map to the tool's purpose. It implies when to use it—for common pitfalls—but does not explicitly contrast with sibling tools or state when not to use it. The context is clear but lacks direct exclusions.

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