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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful topical scope (stay length, signing, rent, driver's license handling), which helps the agent judge relevance, but says nothing about whether the content is curated/static or how it is returned.

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?

A single compact sentence with the subject front-loaded and the covered topics trailing as a scannable list. Every element earns its place, though the topic list could be slightly tighter.

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 zero-parameter, no-output-schema content tool, the key information an agent needs is what topics are covered, and the description enumerates them. The only minor gap is not indicating the response shape (prose vs. structured Q&A).

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 tool takes zero parameters, so the baseline is 4; there is nothing for the description to explain and it correctly adds no parameter noise.

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 resource precisely: heidi.living's answers to the specific questions guests ask before applying, and enumerates the covered topics. It is clearly a static FAQ-content lookup rather than a link generator (application_link) or a region listing (list_regions). It stops short of a verb like 'returns' but the intent is 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?

Phrasing 'questions guests ask before applying' implies the trigger context (pre-application guest inquiries), but there is no explicit when-to-use or when-to-prefer-siblings statement. An agent must infer that application_link is for the actual form and faq is for explanatory answers.

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