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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Get FAQs' and lists topics, but does not state that the tool returns a list, supports filtering by role/locale, or describe any side effects. The agent cannot infer behavior beyond basic retrieval, making it insufficiently transparent.

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 sentence that is front-loaded with the action ('Get Immoswipe FAQs') and concisely lists the FAQ categories. No wasted words or redundant detail.

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 simple nature of the tool, the description covers the basic purpose, but with no output schema and no annotations, it does not explain response format, how role/locale affect results, or filtering behavior. These gaps are moderate for a straightforward FAQ retrieval task.

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 schema describes two of three parameters (role and search_by) with meaningful text, and locale is self-documenting via enum. The description itself adds no parameter-specific meaning, leaving the schema to handle parameter semantics. This is adequate but not enhanced.

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 the tool retrieves Immoswipe FAQs and specifies the covered topics (platform usage, renting, listing, photography/tour services, pricing). This distinguishes it from sibling tools like get_guide and search_guides, which handle guides rather than FAQs.

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 implies this is the tool for FAQ-related queries, but it does not explicitly say when to use it over alternatives or mention any when-not-to-use conditions. Context is clear from the topic (FAQs), but there is no explicit guidance about choosing this vs. other guide tools.

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