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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered by structured data. The description adds genuinely useful behavioral policy not present in the annotations: answer strictly from returned fields and refuse/redirect rather than guess when data is absent.

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?

Three short sentences, front-loaded with the purpose and followed by the grounding and fallback rules. Nothing is redundant and every sentence changes agent behavior.

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?

With one required parameter, full schema coverage, and no output schema, the definition covers what an agent needs: what comes back ('full record' incl. description) and how to behave when the record lacks the answer. It could briefly note behavior for a missing/invalid id, which keeps it from a 5.

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% and the single id parameter is documented with an example ('HH-1001'), so the schema carries the full burden. The description adds no syntax, format, or validation detail beyond it, which matches the baseline 3 for a fully documented 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 names a specific verb and resource ('Return the full record of one listing') plus what the record contains ('including its description text'). It implicitly distinguishes itself from sibling search_listings by scoping to a single record, though it never names the alternative explicitly.

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?

It gives a clear grounding rule ('Answer only from fields present here') and an explicit when-not path ('If the answer is not in the record... hand off with reason not_answerable_from_listing instead of guessing'), which routes the agent to the hand_off_to_human sibling. It does not state prerequisites for obtaining the listing id, but the context of use is clear.

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

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, closed-world write, and the description's "Create a ticket" is consistent with that. It adds useful behavioural context about how the summary is consumed ("so the human does not have to reread the thread"), but does not say whether the customer is notified or what happens after the ticket is filed.

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 sentences, front-loaded with the action and then the escalation trigger list. The long MUST clause is dense but every item earns its place as a routing rule; only the trailing summary instruction could be tightened slightly.

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 4-required-parameter escalation tool with no output schema, the description covers routing, required intent categories, and summary style. It leaves contactEmail semantics and any post-creation behaviour (ticket id, notification, SLA) unspecified, which is a minor but real gap.

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 only 25% (only listingId is documented in the schema). The enumerated use cases in the description map well onto the reason enum values, and the summary wording gives a length/style expectation, but contactEmail (whose address, required even when the listing is unrelated) and listingId's null case are never explained in the description.

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 opens with a specific verb and resource: "Create a ticket for the letting or sales team." That is unambiguous and clearly distinct from the sibling tools search_listings and get_listing, which read listing data rather than escalate an inquiry to a human.

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?

It gives an explicit MUST-use list (viewing bookings, price/rent negotiation, contract or legal, complaints, personal data requests, and anything the listing record cannot answer) plus the exclusion "not answer yourself," which implicitly routes answerable questions to get_listing. When-to-use and when-not-to-use are both covered.

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

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 return behavior not present in structured data: results are summaries sorted by price, cheapest first. It does not address pagination or how the limit truncates results, so it stops short of full transparency.

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?

Three tight sentences with zero filler. The filter criteria and the primary usage condition are front-loaded, and the exclusion/alternative follows immediately after.

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 read-only search tool with no output schema, the description supplies the return shape (summaries sorted by price) and the routing rule to get_listing. It omits the limit/default page size and never mentions propertyType, which is a minor but real gap.

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 50%, so several parameters (offerType, minRooms, minAreaSqm, propertyType, limit) lack schema descriptions. The description compensates by naming rent-or-sale, price ceiling, rooms, area and move-in date as filter criteria, covering most undocumented params, though propertyType and limit remain unmentioned anywhere.

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 opens with a specific verb+resource ("Find listings") and enumerates the hard criteria it filters on, so the agent knows exactly what the tool retrieves. It also explicitly contrasts itself with get_listing, making it distinguishable from its sibling without opening either 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?

It states the triggering condition ("Use this when the inquirer states requirements") and an explicit exclusion with the correct alternative ("Do not use it to answer questions about a specific listing's details; call get_listing for that"). Both when-to-use and when-not-to-use are covered.

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