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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions subscribing and registering a callback URL, but does not describe side effects (e.g., creating a persistent subscription), whether duplicate URLs are rejected, authentication requirements, or how to undo the operation. This is a meaningful gap for a mutation-style tool.

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, focused sentence that conveys the core purpose without wasted words. It is front-loaded with the action and resource, making it easy to scan.

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?

The tool is simple: two fully documented parameters, no nested objects, and an output schema is present. The description plus schema provides enough to understand what the tool does and how to invoke it. It is only missing richer usage-alternative and behavioral-context details, which are already penalized in their respective dimensions.

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%, so the input schema already documents both parameters. The description does not add significant extra meaning beyond the schema; it only restates the callback URL concept already present in the url parameter 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 states a specific verb ('Subscribe') and resource ('OwnerRez events') and explains the mechanism ('registering an HTTPS callback URL'). It clearly distinguishes itself from the sibling list_webhook_subscriptions and delete_webhook_subscription tools by indicating this is the creation operation.

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: use this when you want to receive OwnerRez event notifications via a callback URL. However, it provides no explicit guidance about when not to use it or how it relates to the sibling list/delete webhook subscription tools.

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?

With no annotations provided, the description carries the burden of behavioral disclosure. It discloses that the operation is blocked in read-only mode, which is a valuable behavioral constraint. However, it does not state whether deletion is permanent, idempotent, or any side effects, which are important for a destructive operation.

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 concise, with two short sentences. The core action is front-loaded, and the read-only note is additional relevant information. No redundant or filler words.

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 deletion tool with a single parameter and an output schema provided, the description covers the core action, the parameter meaning, and a behavioral constraint. It does not describe error cases or confirm whether deletion is permanent, but given the simplicity and the output schema, it is reasonably complete. The lack of annotation coverage is partially mitigated by the read-only note.

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 only defines subscription_id as an integer with 0% schema description coverage. The description compensates by stating the action removes a subscription 'by its ID', clarifying that the integer parameter represents the identifier. This adds the necessary semantic meaning beyond the raw schema.

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 action (Remove) and the resource (webhook subscription) with the identifying parameter (by its ID). It distinguishes itself from sibling tools like list_webhook_subscriptions and create_webhook_subscription by its destructive verb, though it does not explicitly name them.

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 provides limited usage guidance. It implies this tool is for removing a specific webhook subscription, and the note 'Blocked in read-only mode' tells the agent when not to use it. However, it does not explain when to choose this over other operations or provide any conditions or prerequisites.

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. The note that 'OwnerRez bounds this endpoint by created_since_utc' is a genuine and useful constraint disclosure, but the description omits read-only safety, pagination behavior, ordering, and what happens when max_items is reached. For a zero-annotation tool, this is a substantial 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 sentences with the core purpose front-loaded and no filler. The second sentence is slightly indirect, attributing the constraint to 'OwnerRez' rather than describing the tool's behavior directly, but it earns its place as a meaningful caveat.

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?

An output schema exists and all parameters are documented, so return values and parameter semantics are largely covered. The description is adequate for a simple search/list tool but misses explicit usage guidance and behavioral detail such as pagination, and the absence of annotations raises the burden the description must carry.

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%, so the schema already documents all three parameters, giving a baseline of 3. The description adds minor value by framing created_since_utc as an endpoint-level bound rather than just a parameter default, but it adds nothing about query or max_items beyond the schema.

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?

'Search or list guests' is a specific verb+resource statement that clearly identifies what the tool does and covers both operating modes (search by query, list all). It doesn't explicitly name sibling tools for differentiation, but no sibling in the provided set is guest-related, so the tool is naturally distinct.

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?

No when-to-use guidance is provided. There is no mention of alternatives, prerequisites, or conditions that should select this tool over others. 'Search or list guests' carries only the barest implication of usage, with no guidance on when to search versus list or what to do when results are bounded.

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Get' conveys a read operation, but this merely restates the tool name; it does not disclose side effects, error behavior, permissions, or the effect of include_guest on the response. The description adds no meaningful behavioral context beyond the verb.

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 sentence with no redundant words; the key identifier and scope are front-loaded. It is appropriately concise, though the brevity leaves some semantic gaps that could be addressed without bloating the description.

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?

The output schema covers return values, but the description is incomplete for an agent: include_guest is entirely unexplained, and there is no guidance about when to use this tool versus list_bookings. For a simple two-parameter getter, the missing include_guest semantics is a meaningful 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 description coverage is 0%, so the description must compensate. It adds meaning to booking_id ('OwnerRez ID') but says nothing about include_guest, which is undocumented in the schema and whose behavioral impact (including guest details) is left entirely to inference.

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 ('Get'), a precise resource ('single booking'), and the required identifier ('OwnerRez ID'). This clearly distinguishes it from siblings like list_bookings, which returns multiple bookings, and who_is_staying, which focuses on current guests.

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 phrase 'single booking by its OwnerRez ID' implies it is for retrieving one known booking rather than listing many, but the description does not explicitly say when to prefer this over list_bookings or mention any alternatives. Usage context is present but only implicitly.

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not explicitly state that this is a read-only operation, nor does it describe potential errors, rate limits, or other side effects. The only behavioral hint is mention of the raw webhook payload in the return, which partially discloses the response format.

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, front-loaded sentence with zero wasted words. It conveys the action, resource, and a distinguishing detail efficiently.

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 that an output schema exists (not shown but indicated), the description needn't explain return values, and it does hint at the payload inclusion. However, it lacks usage context, such as when to use this tool vs. listing messages, and it doesn't clarify behavior on missing events or error conditions. For a simple read operation this is adequate but not rich enough for complete guidance.

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 0%, so the description must compensate. It says 'by id,' which clearly implies the single event_id parameter is the identifier, but it doesn't elaborate on the parameter's meaning, format, or any constraints beyond being an integer. This adds some meaning but not enough to fully compensate for the complete absence of parameter documentation in the schema.

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 a specific verb (Get) and resource (one stored message event) and adds the critical detail that it includes the raw webhook payload. It clearly differentiates from sibling list_messages, which implies listing, without needing to name it 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?

No guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or scenarios where a different tool (e.g., list_messages) would be more appropriate. The agent must infer usage from the name and context.

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals a non-obvious fact: the server filters by since_utc and always sends a time bound, while arrival filters are applied client-side. This goes beyond the schema, which only describes parameter types and defaults. It doesn't cover pagination or error handling, but for a list tool with an output schema, the core behavioral nuance is addressed.

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 precise sentences, no fluff. The purpose is stated first, followed immediately by the critical nuance. Every word contributes to correct usage, making it highly efficient.

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 that an output schema exists and all parameters are documented in the schema, the description covers the one non-obvious behavioral aspect that could cause incorrect invocation. Nothing essential is missing for an agent to call this tool correctly. It is complete for its role.

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%, so all parameters have descriptions. The description adds value by clarifying the relationship between since_utc (always sent, default 180 days ago) and arrival_start/arrival_end (client-side filters). This additional context helps an agent understand the semantics of the time-bound filter beyond the schema defaults. Since coverage is high, the baseline is 3, and this extra guidance earns a 4.

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 'List bookings' — a specific verb and resource. It is clearly distinct from sibling tools like get_booking (singular) and other list_* tools (list_properties, list_quotes, etc.). No ambiguity about what the tool does.

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 explicitly explains the key usage constraint: the endpoint is bound by since_utc (time-based), not stay dates, and directs the user to use arrival_start/arrival_end for stay-window narrowing. While it doesn't name alternative tools for exclusion, it provides actionable guidance that prevents a common misuse. This is more than 'implied usage' but stops short of full alternative comparison.

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?

No annotations are present, so the description carries the full burden. It only says 'List', implying read-only, but fails to disclose details like pagination behavior (max_items), ordering, required permissions, or the effect of null booking_id. This is a minimal description that adds little beyond the obvious fact that it retrieves fees.

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, front-loaded sentence that captures the core action and the key optional filter. There is no redundant wording, and every element is purposeful.

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?

As a simple listing tool with two optional parameters and an output schema, the description covers the essential purpose, but it omits any explanation of max_items and provides no behavioral context (e.g., ordering, authentication, or null behavior). The output schema likely handles return structure, but the description still leaves the agent with unaddressed questions.

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?

With 0% schema description coverage, the description must explain all parameters. It implicitly covers booking_id via 'optionally for a single booking', but says nothing about max_items, leaving that parameter undocumented. The description does not compensate for the schema gap.

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 a specific verb ('List'), a clear resource ('booking fees'), and an optional filter ('optionally for a single booking') that distinguishes it from siblings like list_bookings or list_payments. It leaves no ambiguity about the tool's core function.

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 gives a context clue that fees can be scoped to a single booking via booking_id, but it does not mention alternatives or specify when to choose this tool over related siblings (e.g., list_payments, list_quotes). The agent must infer selection from the resource name alone.

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?

No annotations, but description only says 'list', implying read-only. Does not mention that it respects include_drafts/include_attachments flags or any side effects. Minimal 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?

One clear sentence with no redundant words.

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?

Covers the core function, but omits any mention of pagination or default behavior. However, output schema may cover return format. Slightly incomplete but acceptable for a list tool.

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 fully describes all five parameters with descriptions. Description adds no extra meaning beyond mentioning 'conversation thread', which is already in schema. Baseline 3.

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?

Clearly states verb and resource: lists messages in a thread. Distinguishes from other list tools by specifying thread context.

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?

No mention of when to use this vs alternatives like send_message or list_open_messages. Lacks explicit guidance.

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?

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states that only unhandled inbound guest messages are included, and that messages are captured by the webhook receiver. It also notes the prerequisite that the webhook receiver must be running and subscribed, which is valuable behavioral context. However, it doesn't mention whether the list is sorted by arrival time or if pagination is used beyond the limit parameter, but these are minor gaps.

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 concise and well-structured. It opens with a clear summary, then details what each entry contains, and ends with a critical prerequisite. Each sentence serves a purpose: the first defines the tool's function, the second aids in understanding output and usage, and the third provides necessary operational context. No unnecessary words or repetition.

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 a single optional parameter, no annotations, and an output schema (which likely describes the entry fields), the description is quite complete. It explains the tool's purpose, the content of entries (including thread_id for use with send_message), and the prerequisite for it to work. It could be more explicit about the 'limit' parameter's effect, but this is minor and the output schema likely covers the return format. Overall, an agent has sufficient information to correctly call the tool.

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 description coverage is 0%, so the description must compensate for the undocumented 'limit' parameter. While the description does not explicitly describe 'limit', the context signal shows a single integer parameter with a default of 50, and the description mentions 'each entry includes...' implying a list. However, the description does not explicitly state that 'limit' controls the maximum number of entries returned, so there is a slight gap. Nonetheless, the description's focus on the inbox concept and the fact that limit is optional with a default provides enough context for an agent to infer its purpose.

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's purpose: listing inbound guest messages that are not yet handled, and explicitly frames it as the user's 'open messages' inbox. This distinguishes it from siblings like list_messages and mark_message_handled, as the focus is specifically on unhandled inbound messages from the webhook receiver.

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 specifies when to use this tool (to view unhandled inbound guest messages) and provides actionable guidance: it requires the webhook receiver to be running and subscribed, and refers to create_webhook_subscription with category 'message' for setup. It also implicitly contrasts with sibling tools like list_messages (which likely lists all messages) by focusing on the open inbox.

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?

With no annotations, the description carries the full burden of disclosing behavior. It mentions the fields returned but does not clarify whether the result is sorted, limited, paginated, or whether the max_items parameter is a hard limit. It does not state if the operation is read-only (though 'list' implies it) or if any side effects occur. This is a significant 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?

The description is a single, concise sentence that front-loads the purpose and the key output fields. Every word earns its place, with no filler or redundancy.

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?

Simpler schema and one optional parameter, but no annotations and no output schema details provided in the description. The description is adequate for a simple list tool but lacks guidance on the max_items parameter, pagination, or any edge cases. An agent can call it, but may misuse the parameter or expect unsupported behaviors.

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 0%, so the description must compensate for the undocumented 'max_items' parameter. The description does not mention it at all, which is a gap. However, there is only one parameter with a default value; the schema itself provides the name and default, and the description's omission is not critical. Baseline for 0 params is 4, but here there is 1 param with 0% coverage, so the description fails to add any semantic clarity. Yet the parameter is self-explanatory ('max_items' means maximum number of items), so a score of 4 is justified.

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 verb 'list' and the resource 'property owners', and lists the fields returned (id, name, contact). This is clear and specific enough to distinguish it from siblings like list_bookings or list_properties. However, it does not explicitly contrast with other list tools, but the resource name is sufficient.

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 provides no guidance on when to use this tool versus alternatives, no mention of the max_items parameter or pagination behavior, and no mention of any prerequisites. The agent is left to infer that it is for retrieving owner lists, but there is no context for selection among the many list tools.

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?

With no annotations, the description carries the full burden of disclosing behavioral traits. It only states 'List', implying a read-only operation, but does not explicitly confirm non-mutating behavior, permissions, or any side effects. No additional behavioral context is provided.

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, focused sentence that front-loads the core purpose and includes the optional filter. It is concise and avoids redundancy, making it easy to parse quickly.

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?

The description is minimal and does not clarify what constitutes a 'payment' or any nuances of the data returned. Since an output schema exists, return format is not required, but the lack of context about payment semantics or pagination (relevant to max_items) leaves the tool incomplete for an agent unfamiliar with the domain.

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 description clarifies the booking_id parameter as an optional filter ('optionally for a single booking'), but does not explain max_items at all. With zero schema-level parameter descriptions, this partial clarification adds some value but leaves one parameter completely unaddressed.

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 action ('List') and the resource ('guest payments'), and specifies an optional filter by booking. This is a specific, concise statement that distinguishes it from other list_* siblings like list_bookings or list_properties.

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 via the optional booking filter, but it does not explicitly mention when to use this tool instead of alternatives (e.g., when to use list_payments vs list_refunds). No conditions or exclusions are provided beyond the optional booking parameter, leaving some ambiguity.

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?

There is no information about side effects (though likely read-only), ordering, pagination, or default behavior. The schema parameters (max_items, active_only) are not explained, so the tool's runtime behavior remains opaque.

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, concise sentence that conveys the essential purpose without extraneous detail. It is well-structured and easy to parse.

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?

The description omits explanations of parameters and does not include an output schema, leaving the return format and filtering semantics unknown. This makes the tool incomplete for an agent to use effectively.

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 description does not explain the meaning or usage of the input parameters. Without context, an agent cannot know what 'max_items' or 'active_only' control, nor how they affect the results.

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 action (list) and the resource (properties), with a parenthetical indicating the fields returned. It is unambiguous and distinguishes this tool from siblings like list_bookings or list_owners.

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 provides no guidance on when to use this tool versus alternatives. It does not mention scenarios like filtering by active status or limiting results, nor does it contrast with other list tools.

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?

No annotations are provided, so the description carries the burden of explaining behavior. It communicates a read-only list operation and usefully specifies that property_ids is a comma-separated filter. However, it does not disclose behavior around max_items, pagination, ordering, invalid IDs, or result limits, leaving some behavioral aspects implicit.

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 with the core verb and resource front-loaded, followed by the only important qualifier. It contains no filler, repetition, or unnecessary 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?

For a simple two-parameter listing tool with an output schema, the description covers the essential operation and the main filter detail. However, it omits any mention of max_items behavior and provides no usage guidance, which leaves the description adequate but not fully complete.

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 0%, so the description must compensate for both parameters. It adds meaning for property_ids by explaining the comma-separated filter format, but it says nothing about max_items, its effect, or its constraints. Partial coverage of parameters leaves a clear gap.

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 a specific verb and resource: "List quotes." It also names the optional filtering dimension, and the resource name 'quotes' clearly distinguishes it from sibling listing tools like list_bookings, list_properties, and list_payments.

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 its use case: retrieving quotes, optionally filtered by property IDs. However, it gives no explicit guidance about when to choose this tool over alternatives, nor does it mention any exclusions or conditions. The intended usage is understandable but not fully articulated.

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?

There are no annotations provided, so the description must carry the burden of behavioral disclosure. It says the tool lists refunds (a read operation) and optionally filters by booking, which implies a safe query. However, it does not mention pagination behavior (max_items), ordering, or what fields the returned refunds contain. The output schema exists but is not shown, so the description adds minimal behavioral context beyond the basic read operation.

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 concise sentence that is easy to parse. It front-loads the primary action and resource, with the optional modifier appended. No wasted words, though it barely earns its place given the lack of parameter and usage 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 tool has an output schema (which handles return values) and two simple optional parameters, the description is thin. It does not cover the max_items pagination parameter, which is a common need, nor does it clarify the relationship to list_payments for refund-specific queries. The context of guest refunds vs. property payments is left undefined, so an agent may under-specify calls.

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 0%, meaning the description does not explain any parameters. The input schema includes max_items (with default 100) and booking_id (nullable), but the description only hints at the booking filter. The max_items parameter is completely undocumented, and no parameter semantics are added beyond what the schema's name and type imply.

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 a clear verb ('List') and resource ('guest refunds') and notes an optional filter ('optionally for a single booking'). It is specific enough to distinguish from siblings like list_payments or list_bookings, though it could more explicitly contrast with list_payments since refunds are a subset of payments.

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 a default use case (listing all refunds) and an alternative (filter by booking_id), but it does not explain when to use this tool versus list_payments or other financial tools. No explicit exclusions or prerequisites are stated, leaving some ambiguity for an agent deciding between refunds and payments.

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?

No annotations exist, so the description bears the responsibility for behavioral disclosure. It does not state whether the operation is read-only, if there are side effects, permissions required, or any limitations. The only implied behavior is that it lists active subscriptions, but this is part of the purpose rather than a transparency trait.

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, concise sentence with no redundant words. It directly states the action and scope, achieving high efficiency.

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 list operation with one parameter, the description is too sparse. It does not explain the return format, the meaning of max_items, or any caveats. Even though the sibling tools are clear, the missing parameter semantics and behavioral details make the description incomplete.

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 only parameter, max_items, is described only by its schema (integer, default 200). The description provides no explanation of its meaning or effect, and since schema coverage is 0%, the description fails to compensate. The purpose of max_items is not inferable from the minimal 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 clearly states the verb 'List' and the resource 'webhook subscriptions', further scoped by 'active' and 'on the account'. This distinguishes it from sibling tools like create_webhook_subscription and delete_webhook_subscription.

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 purpose is clear enough to infer when to use this tool versus creating or deleting subscriptions, but it does not explicitly mention alternatives or exclusions. The context is clear but lacks explicit guidance.

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?

With no annotations, the description carries the full burden of behavioral disclosure. It does this well: it explains that the tool toggles handled state, removes the message from the open list, supports reopening, and that it is local-only with no OwnerRez call. This gives an agent a clear mental model of side effects beyond a mere command name.

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 short sentences with no filler. The primary action is front-loaded, and every phrase earns its place—especially the useful caveat that this is local bookkeeping only.

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 two-parameter local toggle with an output schema available, the description is mostly complete. It covers behavior, side effects, and the external-system boundary. The main gap is the lack of explicit parameter documentation, but the schema provides types, requiredness, and the default, so the description is sufficient for an agent to invoke this 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 0%, so the description must compensate, but it never explicitly explains event_id or handled. The phrases 'handled (or reopen it)' and 'removing it from the open list' hint at the handled boolean and the message identity, but the meaning of event_id and the role of the handled default are left to inference.

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 uses a specific verb ('Mark'), a clear resource ('a stored message'), and states the effect ('handled (or reopen it)', 'removing it from the open list'). It also distinguishes itself from siblings by explicitly noting it is local bookkeeping and does not call OwnerRez, so an agent can tell it apart from message-related operations like send_message or list_open_messages.

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 provides clear context about when this tool is appropriate: it is for local bookkeeping of message handled-state, and explicitly warns that it does not call OwnerRez. This functions as a when-not-to-use signal, though it does not name an alternative tool or give more detailed decision criteria.

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?

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does disclose the operation is a mutating send on an existing thread, which implies it won't create a thread. But it doesn't mention failure conditions (e.g., invalid thread_id), delivery semantics, permissions, or attachment behavior beyond what the schema already states.

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 sentence with verb, resource, and constraint, front-loaded with the verb 'send.' There is no filler and every word earns its place. Slightly more could be added given the absence of annotations, but as a structure it is appropriately sized.

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 moderate-complexity tool with fully described parameters and an output schema, the description covers the core what. Missing are usage routing against message-management siblings like mark_message_handled, and any failure-context hints. Since no annotations exist, the description is adequate but not genuinely enriching.

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% — body, thread_id, and attachment_url each have descriptive text, including how to learn the thread ID and the ~5MB attachment cap. The description adds no meaning beyond the schema beyond characterizing the recipient as a guest, so the baseline 3 applies with the schema doing the heavy lifting.

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 a specific verb and resource ('Send a message') plus the context ('to a guest on an existing conversation thread'). This clearly distinguishes the action from read-oriented siblings like list_messages and get_message_event. However, it never names an alternative explicitly, so the differentiation is implicit rather than stated.

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 phrase 'existing conversation thread' implies the tool requires a pre-existing thread and will not create one, which is a meaningful usage constraint. But the description gives no explicit when-to-use/when-not-to-use guidance or alternatives, and the prerequisite on how to obtain thread_id lives in the schema, not the description. Usage is implied, not spelled out.

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?

With no annotations present, the description carries the full behavioral burden. It discloses the active-stay filter (arrival <= on_date < departure), the default of today, and the internal '~year' lookback limitation. This is transparent about both output semantics and data freshness constraints, which is exactly the kind of behavior an agent needs to know.

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: purpose, row structure, and behavior/default. Every sentence adds distinct value without redundancy. The most critical information (what it shows) comes first, and the internal limitation is placed at the end without clutter.

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?

The description covers the tool's purpose, output shape, default behavior, and a key limitation (~year lookback). Given the presence of an output schema (even though not shown) and the single optional parameter, nothing essential is missing. An agent can call this correctly with the information provided.

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 only provides a nullable on_date with no description. The description clarifies that on_date defaults to today and that it's used to determine which stays are active, effectively explaining the parameter's role. It stops short of specifying the date format (e.g., ISO 8601), but given the low schema coverage, this is strong compensation.

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 'Show who is currently staying in each property (in-house guests)' which is a specific verb+resource combination. It further clarifies scope with 'one row per active stay' and the date condition, making its purpose unambiguous. While it doesn't name a sibling, the purpose is distinct enough on its own.

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 ('Defaults to today') but does not explicitly contrast with alternatives like list_bookings or find_guest. No when-to-use or when-not-to-use guidance is given, leaving the selection to inference from its unique 'in-house guests' framing.

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