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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful context about the scope of content (categories like check_in, parking, emergency) and that it returns 'all' FAQs, but does not mention pagination, response format, or behavior when no FAQs exist. This is moderate added value beyond annotations.

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 two concise sentences, front-loaded with the primary purpose. The first sentence states what the tool does, the second elaborates on categories. No wasted words or redundant information.

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 simple read-only tool with two parameters and no output schema, the description is adequate. It explains the content and filter options, implying that the response contains question-answer pairs. It does not detail edge cases like empty results, but the overall context is sufficient for an agent to invoke the 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?

Schema description coverage is 100% for both property_id and category. The description repeats the category list but does not add new parameter meaning beyond what the schema already provides. This aligns with the baseline score of 3 for full schema coverage.

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 'Get all frequently asked questions and answers for a vacation rental property' with a specific verb and resource. It also lists the content areas (WiFi password, check-in instructions, etc.) and distinct filter categories, making it distinct from sibling tools like 'ask_vacation_rental_question' or 'get_vacation_rental_house_rules'.

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 usage for retrieving FAQ content and mentions filtering by category, but does not explicitly state when to use this tool versus alternatives like 'ask_vacation_rental_question'. No exclusions or alternative tool names are provided, so guidance is implied rather than explicit.

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