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

Annotations already signal readOnlyHint and openWorldHint, so the safety profile is covered. The description adds useful behavioral detail beyond the annotations: default dropping of rating-icon and incidental image URLs, plus the view:"full" escape hatch that returns TripAdvisor's whole record. This gives an agent a clearer expectation of response-shape 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?

Two sentences, zero filler, with the core purpose front-loaded and the important view behavior in the second sentence. Every clause adds information an agent needs.

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 single-location detail tool with full schema coverage and readOnly/openWorld annotations, the description covers the return content, the full-record option, and the filtering default. There is no output schema, so the explicit field list helps compensate, and nothing essential 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?

Schema description coverage is 100%, and the schema already documents locationId, locale, and view with their meanings and enum options. The description adds no meaningful parameter semantics beyond what the schema contains, so the baseline of 3 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?

The description opens with a specific verb and resource, 'Get full details for a TripAdvisor location,' and enumerates the exact field categories returned (names, descriptions, address, coordinates, ratings, phone, category, listing URLs). This clearly differentiates it from sibling tools like photo/review/search tools, even without naming 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 does not state when to use this tool versus alternatives such as ta_search_locations or ta_get_locations. It mentions the view option but gives no explicit guidance about prerequisites, exclusions, or the search-tool origin of locationId; that context only appears in the schema.

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 description adds behavioral context beyond annotations by specifying the output (URLs, source, dimensions) and pagination support. Annotations already indicate readOnlyHint and openWorldHint, and the description aligns with those without contradiction.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence that efficiently conveys the purpose and key return data. It is front-loaded and contains no unnecessary 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 read-only tool with good annotations and a self-documenting schema, the description provides sufficient context about output and pagination. It could be improved by noting the necessity of locationId from a search, but schema already covers that.

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% (all 4 parameters have descriptions). The tool description does not add additional meaning beyond what is already in the schema; it only mentions pagination which is implied by page and size parameters.

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 'Get photos' and the resource 'TripAdvisor location', and specifies the returned data: 'multi-size image URLs, source, dimensions'. It also mentions pagination, which distinguishes it from sibling tools like ta_get_location_details or ta_get_location_reviews.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving photos, but does not explicitly state when to use versus alternatives or any exclusions. Sibling tool names provide context, but no direct guidance is given.

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 readOnlyHint and openWorldHint annotations already signal a safe, externally-sourced read operation. The description adds useful behavioral detail beyond those annotations: avatars and image URLs are dropped by default, and passing view:"full" returns TripAdvisor's whole records. This helps the agent predict response differences.

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, no filler. The core purpose and pagination are front-loaded, and the important default-vs-full behavior is explained immediately after. Every sentence 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 read-only paginated listing tool, the description covers the essential invocation context: resource, pagination, and response-shape behavior. The schema handles parameter details. It does not describe the output shape, but no output schema exists and the tool's read-only nature lowers the risk of misinterpretation.

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 the schema already documents all parameters. The description adds practical meaning by explaining the default effect of the view parameter and the pagination capability, which helps an agent choose the right values without diving into schema nuances.

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: get traveler reviews for a TripAdvisor location. Saying "traveler reviews" cleanly distinguishes this from the sibling tools for search, details, photos, and general location lookup.

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 makes the context clear: use this tool when traveler reviews for a location are needed. It does not explicitly name alternatives or exclusions, but the sibling names and the singular review focus provide enough directional 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?

The description adds useful behavioral context beyond the readOnlyHint and openWorldHint annotations: it discloses that unknown or unlicensed ids are silently omitted, which is critical for interpreting sparse results. It also notes default vs. full response shapes, though the schema already details this. This is helpful behavior disclosure without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two compact sentences that front-load the core purpose and the key behavioral caveat. Every sentence adds value: purpose, cost comparison, silent omission, and view behavior. No filler or redundant restatement of the tool name.

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 output schema, the description does enough to set expectations for the response (slim summaries vs. full records) and covers the main edge case (silently omitted ids). Locale parameter is left to the schema, which is acceptable. It is complete enough for an agent to decide when and how to invoke, though a bit more detail on the response structure would push it to 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 coverage is 100%, so the schema already documents all three parameters. The description mostly echoes what the schema states (array of ids, full view option) rather than adding new parameter-level meaning. Baseline 3 is appropriate; no additional semantics are introduced 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 clearly states the tool gets details for multiple locations in one batch call, contrasting it with the single-location sibling ta_get_location_details. The verb 'Get' plus resource 'locations' and the MULTIPLE/batch qualifier leave no ambiguity about what this tool does and how it differs from its siblings.

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 explicitly positions the tool as the cheaper alternative to repeated ta_get_location_details calls, giving a clear 'when to use' condition. The note about unknown or unlicensed ids being silently omitted also helps the agent set expectations before invoking and advises against using this when missing ids matter.

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 and openWorldHint, so the bar is lower. The description adds useful behavioral context beyond those annotations: results are slim by default, pagination is included, and view:"full" returns complete records. This is meaningful for an agent deciding whether the default response is sufficient.

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 sentences with no filler: the action and scope come first, followed by the output contract and the key view modifier. Every sentence 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 search tool with no output schema, the description sufficiently conveys what the agent can expect: location ids, pagination, and slim-vs-full response shapes. The remaining parameter details are fully covered by the input schema, though the description could have briefly mentioned scoping filters like geo_name or postal_code.

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 the baseline is 3. The description adds value by mapping the categories to "restaurants, attractions, hotels" and clarifying the effect of the view parameter between slim and full records, which complements the schema's enum descriptions.

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 a specific action (search TripAdvisor locations by name) and resource type (restaurants, attractions, hotels). It also explains the key output (location ids for detail tools) and pagination, which helps position it against the get_* and search_nearby siblings, though it does not explicitly name a sibling.

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 the intended workflow: search by name, then use the returned location id with the detail tools. It does not explicitly state when to prefer ta_search_nearby or ta_get_locations instead, nor does it mention exclusions such as searching by coordinates.

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=true and openWorldHint=true. The description adds useful behavioral detail beyond that: it states that results include distance and a location id, and that slim summaries are returned by default while view:'full' returns whole records. This helps the agent understand response shape expectations.

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 only two sentences, front-loads the core purpose, and every clause adds information: the spatial modes, the response fields, and the view switch. There is no filler or repetition of schema details.

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 high parameter count, 100% schema coverage, and no output schema, the description is adequately complete: it explains the essential invocation modes and the output shape. It could go slightly further by explicitly stating that the three center modes are mutually exclusive, but the word 'or' conveys that reasonably well.

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 each parameter. The description adds semantic grouping by explaining that lat+lon, location_id, and sw/ne bbox each serve as different center/region modes, and clarifies the meaning of the default versus full view. This exceeds the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb and resource: 'Find TripAdvisor locations near a point within a radius, or inside a bounding box.' It clearly differentiates this tool from siblings like ta_search_locations and ta_get_locations by emphasizing geospatial proximity search, so an agent can tell what this tool is for without opening the 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?

The description provides clear usage context by enumerating the three supported center modes: lat+lon+radius, location_id+radius, and sw/ne bounding box. It does not explicitly name alternative sibling tools or tell the agent when not to use this tool, but the mode guidance is concrete and actionable.

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?

Discloses behavioral traits beyond annotations: reads from public page via browser bridge, works without API key, does not return individual review text. Annotations already declare readOnlyHint and openWorldHint, and description adds useful context.

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 sentences, front-loaded with the main action, no unnecessary words. Every sentence adds value.

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's simplicity (1 parameter, no output schema), the description adequately lists return fields, covers supported location types, and notes what it does not return. Complete for agent decision-making.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% for the single parameter locationId, and the description repeats the same description from the schema without adding new semantic meaning. Baseline 3 is appropriate.

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 gets core TripAdvisor location details by ID, listing specific fields, and distinguishes from sibling ta_get_location_details by noting it uses browser bridge and works without API key.

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?

Explicitly says to use this tool when ta_get_location_details is unavailable or its key is blocked, providing clear context for when to use vs alternative.

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 declare readOnlyHint, openWorldHint, and idempotentHint. The description reinforces read-only with 'Read-only, no auth required' and adds substantial behavioral detail: it explains the returned diagnostics and distinguishes three failure modes ('bridge never came up' vs 'extension not connected' vs 'real www.tripadvisor.com-side problem'). This goes beyond what annotations provide and gives the agent a precise mental model of the tool's 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, information-dense paragraph that front-loads the purpose and then enumerates the diagnostics. Every clause contributes value, and it is not overly verbose. It could be slightly more compact by splitting into bullet points, but it is readable and well-structured.

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 output schema, the description fully explains the return values (role, port, version, extension link state, elapsed time, hint). It also covers the calling scenario and failure interpretation, leaving no critical gap for a zero-param diagnostic tool. The description is complete for an agent to understand when and how to use it.

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 schema coverage is 100% trivially. Per the baseline for 0 params, a 4 is appropriate. The description mentions the input URL (a small public www.tripadvisor.com URL) but since no parameters exist, there is no need to elaborate further.

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 ('round-trips'), a resource ('fetchproxy bridge'), and lists the diagnostic outputs (role, port, version, extension link, elapsed time, hint). It is clearly distinct from the sibling tools, which all fetch location data, by focusing on infrastructure health rather than content.

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 an explicit trigger: 'Call this when a real tool fails and you want to know which hop broke.' It does not name specific alternatives, but the context of siblings (location-fetching tools) makes it clear this is for diagnostics, not data retrieval. It lacks an explicit 'when not to use' but the condition is strong.

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