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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered; the description adds real value beyond that by specifying the not-found behavior for uncollected hosts and that only public profile data is returned. It does not discuss caching or freshness of the dataset, which is the only notable remaining gap.

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 tight sentences: the first front-loads what is returned and by what key, the second carries the id source and the error case. No repetition of the name or 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?

For a single-parameter lookup with an output schema already defining the return shape, the description covers purpose, id provenance, and the not-found case — everything an agent needs to call it and interpret a miss. The field list is redundant with the output schema but cheap and harmless.

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 coverage is 100% and the parameter already documents "Numeric Airbnb host id, e.g. 65056940," so the baseline is 3. The description pushes past that by stating acceptable id provenance (host search or room data), which meaningfully constrains what value to pass.

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 and resource ("Returns one Airbnb host's full public profile from the dataset by numeric host id") and enumerates the returned fields, so an agent can distinguish it from datasets_airbnb_hosts_search and datasets_airbnb_hosts_facets without opening a 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 tells the agent where the required id comes from ("a host_id from datasets_airbnb_hosts_search or an Airbnb room"), establishing the search-then-fetch workflow, and adds the failure condition ("returns not found when the host is not collected yet") so the agent knows how to interpret an empty result.

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