CampWatch

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

Annotations already cover readOnly/idempotent/openWorld/destructive semantics, but the description adds genuinely useful non-structured context: results are snapshots and errors do not prove absence of availability. That error-semantics caveat is real behavioral value beyond the annotations, though return format and rate/refresh behavior are not 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 tight sentences with zero waste; the core action is front-loaded and the important error caveat follows immediately. Nothing is redundant with the title.

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 so return values need not be explained, and annotations cover the safety profile. However, for a 7-parameter tool at 0% schema coverage, the description leaves parameter formats and provider/slug semantics undocumented, leaving 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 schema documents nothing about the 7 parameters. The description conceptually maps them (campground, dates, party size) which partially compensates, but adds no format details for checkIn/checkOut, the provider/slug relationship, or adult/child/infant limits.

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 (Check) and resource (current availability for a campground) with the key inputs (dates and party size). It is distinguishable from siblings like find_campgrounds and list_providers, though it does not explicitly contrast itself with 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 gives no when-to-use guidance, no prerequisites, and no named alternative (e.g., find_campgrounds to locate a campground vs. this tool to check its availability). Usage is only implied by the verb.

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 idempotentHint=true, destructiveHint=false, openWorldHint=true. The description earns credit beyond them by specifying the channel (SMS/push), the concrete idempotency contract for retries, and the side effect that available-now results can consume an alert credit. It still omits notification-delivery behavior and how existing alerts interact.

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, front-loaded with the action and the approval precondition, then the idempotency rule and the credit caveat. No filler, though the credit sentence is vague enough that it earns less than its space.

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 so return values need no explanation, and the description covers the approval gate, idempotency, and billing side effect. However, for a 7-parameter creation tool with three undocumented filter parameters, the guidance is not complete enough to call it confidently.

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% across 7 parameters including nested objects, so the description must carry the load. It names target, dates, partySize and idempotencyKey conceptually, but watchOptions, siteTypeFilter and excludedCampgroundSlugs go entirely unexplained in both schema and 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?

States a specific verb and resource: creates an SMS/push availability alert, and names the key inputs (target, dates, party size) plus the idempotency contract. It does not explicitly contrast itself with siblings like list_alerts, stop_alert, or check_availability, but the action 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?

Gives a real precondition (create only after the user approves target, dates and party size) and idempotency usage rules (new key per intended alert, reuse on retries). It never says when to prefer this over check_availability or enable_sms_alerts, so routing guidance is only partial.

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, idempotentHint=true, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds only that both free and purchased credits are reported, which is modest but relevant context; no auth or scoping caveats are offered.

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 tight sentence that front-loads the verb and resource with zero filler. Nothing is redundant with the name or title.

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 no parameters and an output schema that documents the return shape, the description covers what an agent needs before invoking. The only gap is disambiguation from 'credit_history', which the description never addresses.

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 there is no parameter semantics for the description to explain. Baseline 4 applies.

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 ('Read') and resource ('the connected account's free and purchased alert credits'), naming the two credit categories. It is clear what the tool returns, but it does not distinguish itself from the sibling 'credit_history', which an agent could easily confuse with a balance read.

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 or exclusions are given despite a near-identical sibling ('credit_history') in the toolset. The agent must infer from the name alone whether to call this or the history variant.

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?

The annotations already declare readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is covered. The description adds no behavioral context beyond restating that it is a read, such as authentication requirements, data freshness, rate limits, or pagination/limit behavior.

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 no filler. Given the simple zero-parameter read operation, every word earns its place.

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 zero parameters, an output schema, and rich annotations, the description is close to sufficient for invocation. Its only meaningful gap is that it does not differentiate the tool from the related credit_balance sibling or clarify what "credit ledger" encompasses beyond what the output schema already provides.

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 has zero parameters, so there are no parameter semantics for the description to clarify. Baseline for a zero-parameter tool is 4, and the description introduces no misleading parameter information.

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 ("Read") and resource ("connected account's credit ledger"), so the basic operation is clear. It does not, however, distinguish this tool from the sibling credit_balance, leaving potential ambiguity between reading history and reading a current balance.

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?

There is no guidance about when to use this tool versus alternatives such as credit_balance, nor any stated prerequisites or exclusions. The description merely states what the tool does, not when it should be chosen.

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?

Goes beyond the annotations by disclosing side-effect boundaries: it 'preserves push settings' and 'never starts a purchase,' and it requires explicit user consent. The annotations already establish idempotent, non-destructive, open-world behavior, yet the description usefully clarifies that existing channels are untouched and no billing is triggered.

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 core action and consent gate before the secondary assurances. The 'new phone-linked accounts' sentence is slightly background-heavy but still earns its place by explaining when this call is needed.

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 mutation tool with an output schema and annotations covering the safety profile, the description supplies the remaining essentials: consent precondition, scope, and side-effect guarantees. Nothing an agent needs to invoke it correctly is missing.

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?

Zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The description correctly implies the operation is account-scoped with no configurable inputs.

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 and resource with scope: 'Enable SMS delivery for all alerts on the connected account.' An agent can tell this configures a delivery channel rather than creating/listing/stopping alerts. It never explicitly distinguishes itself from siblings like create_alert or list_alerts, so it falls short of a 5.

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?

Gives a clear precondition ('only after the user approves SMS notification intent') and context for when the call matters ('new phone-linked accounts have no delivery channel until configured'). It implies when-not (already-configured accounts) but names no alternative sibling tool, so no explicit routing.

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, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds the useful handoff detail that provider and slug feed downstream availability/alert calls, but says nothing about pagination, result caps, or coverage limits.

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 short sentences, zero filler, with the scope statement front-loaded before the downstream handoff hint. Every clause earns its place.

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 so return values need no explanation, and the description does cover the downstream workflow. But with five undocumented parameters and cursor-based pagination, an agent still lacks guidance on how to page or shape results.

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% across five parameters (q, limit, state, cursor, provider), yet the description explains none of them. It names "provider" as an output field to reuse but gives no meaning, defaults, or usage for limit, state, cursor, or the free-text q.

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 (Search) and resource (CampWatch's supported Australian campground catalogue), which is distinctive among siblings. However, it does not explicitly contrast itself with list_providers or the alert tools, so the agent must infer the boundary.

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?

"Use returned provider and slug for availability and alerts" tells the agent what to do with the results, implicitly routing to check_availability and create_alert. There is no explicit when-not-to-use guidance, but the workflow context 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 readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds a genuinely important behavior beyond that: the default status filter silently hides stopped and expired alerts unless explicitly requested. Return format is not needed since an output schema exists.

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 short sentences with zero waste. The default-filter behavior is front-loaded, and the value syntax follows immediately.

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 list tool with full annotations and an output schema, the definition covers purpose, default scope, and status syntax. The main remaining gap is pagination/cursor behavior, which is left entirely to the schema's bare cursor field.

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 carry parameter meaning. It explains only the status parameter's accepted values and default; the limit and cursor parameters (including how pagination works) are undocumented in both schema and description. Partial compensation for 1 of 3 parameters is insufficient.

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 (List) and resource (the connected account's alerts), so the agent knows exactly what it retrieves. It does not explicitly contrast itself with siblings like create_alert, stop_alert, or reactivate_alert, but the read-only listing 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?

Gives clear context: default returns only active alerts, and passing 'ACTIVE,STOPPED,EXPIRED' widens to all. That is actionable guidance for the status parameter. It names no exclusions or alternative sibling tools, which is the only gap.

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, idempotentHint, destructiveHint=false and openWorldHint=true, so the safety profile is fully covered without the description. The word 'supported' hints at a static reference set, which adds minor value, but nothing is said about caching, volatility, or result shape.

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 short sentence with no filler, and the key resource is front-loaded. It is arguably too terse to be maximally useful, but it wastes nothing.

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, so return values need not be described, and annotations cover the behavioral profile. For a zero-param reference-list tool, the definition is essentially complete, with only the domain meaning of 'provider' left implicit.

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 are no argument semantics for the description to explain or omit.

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 ('List') and resource ('supported booking systems and regions'), so the agent knows it returns reference data. It does not differentiate from siblings, but the siblings (availability, alerts, credit, campgrounds) are functionally distinct enough that confusion is unlikely.

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?

There is no explicit when/when-not guidance or named alternative. Usage is implied by the zero-parameter, enumeration nature of the tool — an agent can infer this is a lookup for valid provider/region values — but nothing in the text confirms that intent.

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 the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true). The description contributes the ownership/authorization scoping ('owned by the connected account') and the required prior state ('stopped'). It adds modest value beyond structured fields but says nothing about failure modes if the alert is already active or lacks ownership.

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 short sentence with zero redundancy, front-loading the action and resource. Every clause earns its place.

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 state-toggle tool, the description plus an output schema and full annotation set cover almost everything the agent needs. The remaining gap is the unexplained 'id' parameter, but returns and safety behavior are already handled by structured fields.

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% and the single parameter 'id' is undocumented — the description never says what the id identifies or where to obtain it. The schema supplies only type/pattern/maxLength constraints, so the description fails to compensate for the coverage 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?

States a specific verb+resource ('Reactivate a stopped alert') plus a scoping constraint ('owned by the connected account'), so the agent knows exactly what state change occurs. It does not explicitly name stop_alert as the inverse operation, but the pairing is evident from the sibling list.

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 word 'stopped' implies the precondition for calling this tool (the alert must already be stopped), which is useful implicit guidance. However, there is no explicit when-to-use/when-not statement and no named alternative such as stop_alert for the reverse case.

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?

The annotations already declare this is a non-readOnly, idempotent, non-destructive write, so the safety profile is largely covered. The description adds the useful reversibility fact ('It can be reactivated'), which contextualizes state recovery, but says nothing about effects on downstream alerts, notification behavior, or permissions.

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 short sentences, front-loaded with the core action and followed immediately by the reversibility note. 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?

An output schema exists, so return values needn't be explained, and annotations cover the mutation's safety profile. However, for a state-changing tool the description omits what stopping actually does to the alert and how it relates to the reactivate_alert sibling.

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% and the single required 'id' parameter carries only a pattern and maxlength. The description does not say what the id identifies or its format, so it fails to compensate for the missing schema documentation.

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 (stop) and resource (alert) with a scoping qualifier ('owned by the connected account'), so the operation is unambiguous. It does not explicitly distinguish itself from the sibling reactivate_alert tool by name, though the second sentence alludes to the reverse 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?

There is no explicit when-to-use guidance, no prerequisites, and no named alternative among the siblings. The phrase 'It can be reactivated' hints at a reversible workflow that points toward reactivate_alert, but the agent must infer the routing condition itself.

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