KnowNottingHill

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is covered. The description adds that output is 'sourced records' with shared tags, which is genuinely useful, but it says nothing about behavior with invalid or non-existent slugs.

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 sentence, front-loaded with the verb and resource, with the range constraint and return content folded in efficiently. No filler.

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 one-parameter read tool with full annotation coverage and no output schema, the description gives enough: the operation, the input shape, and a hint at the return payload ('sourced records ... shared tags'). Minor gap is the absence of any error/edge-case behavior.

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

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

Schema description coverage is 100% and the single parameter documents the array, uniqueness, and min/max items, so the schema does the heavy lifting. The description's '2 to 4 ... by slug' merely restates the schema constraints rather than adding new semantics.

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: side-by-side comparison of 2-4 Notting Hill places by slug, and says what comes back (sourced records plus shared tags). It implicitly separates itself from get_place (single place) via the multi-slug comparison framing, but never names the sibling 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?

The multi-place comparison framing implies when to use it over get_place, and the '2 to 4' bound implies a minimum viable use. However, there is no explicit when-to-use statement, no mention of what happens if slugs are unknown or duplicated, and no named 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 already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds two useful facts beyond that: only 'published' guides are returned, and fields carry sourcing/provenance. It does not cover pagination behavior, total counts, or the response to an invalid slug.

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 with no filler; the resource and the returned content come first. As a sentence fragment it is terse to the point of being slightly clipped, but nothing is wasted.

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 lookup with no output schema, the description does the necessary work by naming the return shape (introduction plus ranked places) and the publication filter. Pagination and error semantics are left unstated, which is a modest gap for a 2-parameter 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 description coverage is 100%, so both parameters are already documented, including the limit default of 25 and max of 50. The description only restates 'by slug' and never mentions how limit affects the ranked places, so it adds no meaning 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?

The description gives a specific verb-and-resource pair: fetch ONE published Notting Hill guide by slug, and it even enumerates the payload (introduction + ranked places). The word 'one' implicitly contrasts it with the list_guides sibling, but the sibling is never named, so differentiation is inferred 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?

Usage is only implied: 'by slug' suggests you must already have a slug, and the schema note points to list_guides. There is no explicit guidance on when to use this over get_place, list_places, or search_places, and no statement about what to do if the slug is unknown.

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, non-destructive, and closed-world behavior, so the safety profile needs no restatement. The description adds value beyond the annotations by disclosing what the response contains: the editorial description and the public /place URL. It does not say what happens if the slug is unknown.

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 zero filler. The resource and the lookup key come first, followed by what the response contains, so nothing is buried.

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 and a one-parameter read-only tool, the description does enough: it names the record type and two concrete response fields. The only gap is error and empty-result behavior, which is minor for a simple lookup.

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%, and the single parameter carries its own example ('lytte-coffee'). The description's phrase 'by slug' only reinforces the schema and adds no format, casing, or edge-case detail. Baseline 3 applies when the schema does the work.

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-plus-resource formula: 'Full editorial record for one Notting Hill place by slug.' This tells an agent that the tool fetches a single record, which sets it apart from the list_places and search_places siblings. It stops short of naming those siblings as alternatives.

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?

Usage is only implied: the agent is expected to know a slug and want the full record rather than a search. There is no explicit statement such as 'use this after search_places returns a slug' and no statement of when not to use it. It is adequate but lacks routing 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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real value with the 'published' filter and the fields returned (sourced titles, summaries, place counts), but says nothing about ordering, result volume, or empty-state 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?

A single front-loaded sentence with no filler, and the key qualifier 'Published' comes first. The inline URL template with {slug} is slightly noisy for a tool that takes no arguments, but it is compact and informative.

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 no output schema, the description carries the burden of describing return values, and it does so by naming titles, summaries and place counts. Missing only secondary details like ordering or result caps, which are low-stakes for a catalogue listing.

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 the baseline is 4; the schema is empty and there is nothing for the description to disambiguate. The URL template mentioning {slug} is the only parameter-adjacent detail and correctly belongs to the get_guide sibling rather than this call.

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 resource (published Notting Hill themed guides) and even gives the URL pattern, so an agent knows exactly what is returned. It stops short of explicitly contrasting with the sibling get_guide, though the {slug} template hints at that relationship.

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?

Usage is only implied: the word 'Published' and the plural 'guides' suggest browsing a catalogue, which implicitly points at get_guide for detail. There is no explicit when-to-use, when-not, or named alternative among the six siblings.

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, non-destructive, and closed-world behavior. The description adds useful output context via the result page URL pattern and ranked pages path, but it does not explain ordering, pagination, or the complete response 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?

The description is two tight sentences and front-loads the core purpose before adding URL context. Every element is relevant and there is no 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?

For a read-only list tool with four optional filters and no output schema, the description covers the core purpose and gives useful output-link structure. It is largely complete, though it leaves sibling routing and result ordering to be inferred.

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 all four parameters, including enums and the default/max for limit. The description repeats category, tag, and featured in prose but adds little meaning beyond the schema, and 'limit' is not mentioned 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?

States a specific verb ('List') and resource ('places') scoped to Notting Hill, with optional filters. It is clear on its own, but it does not distinguish itself from siblings such as search_places, nearby_places, or get_place.

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 browsing use case through 'Curated places' and lists optional filters, but it gives no explicit when-to-use or when-not-to-use guidance. Routing between this tool and search_places is left to inference.

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 readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds useful behavioral context — that results are curated places, coordinates are WGS84, and distances are in metres — but says nothing about ordering, default radius behavior, or what happens when nothing falls in range.

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 dense sentence with the key facts (proximity, scope, coordinate system, distance unit) front-loaded and no filler. It could be slightly clearer with a brief clause on ordering or defaults, but nothing is wasted.

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?

No output schema exists, so the description should carry more of the return/behavioral burden. It omits result ordering, what 'curated' excludes, whether distance is computed from the supplied point, and how category filters results — gaps that matter for a 5-parameter geo query 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 coverage is only 40%: only limit and radius have descriptions, while category and the two coordinates are undocumented in the schema. The description partially compensates by pinning the coordinate system (WGS84) and the distance unit (metres, tying to radius), but the category enum and its effect on results are never explained.

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?

Names a specific action and resource: nearest curated Notting Hill places to a WGS84 coordinate, returning distance in metres. This is clearly distinct from get_place or compare_places in spirit, but it never explicitly contrasts with the closest sibling, search_places, which likely overlaps in intent.

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 when-to-use guidance and no mention of alternatives among the six siblings. An agent must infer from the name alone whether to call nearby_places, search_places, or list_places for a given lookup.

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 readOnly, idempotent, closed-world behavior, so the description's job is to add context beyond that, and it does: it discloses that addresses, coordinates, hours, websites and photos are NOT returned and that the place url must be followed for them, and it flags that open_now data is unpopulated. A minor gap is that ordering/tie-breaking and result-volume behavior beyond the limit parameter are not spelled out.

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 core purpose and filters, then the return-shape caveat, then the open_now warning. Dense but each sentence earns its place; the middle sentence packs several omissions into one clause, which is efficient rather than padding.

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 carries the burden of describing returns, and it does so by naming what is included (sourced fields) and what is excluded (addresses, coordinates, hours, websites, photos) plus the follow-up url. It stops short of describing result envelope details like total counts or pagination, which is a small residual gap for a 7-parameter search 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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: the ranking model tied to the category slug and the data-availability caveat on open_now, which no schema field conveys. The 'every tag must match' semantic is already in the schema, so it repeats rather than extends there.

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 ('Filter curated Notting Hill places') plus the exact dimensions it filters on and the ranking model ('ranked like https://knownottinghill.com/best/{category}'). It never names siblings such as list_places, nearby_places, or compare_places, so an agent must infer the boundary itself, which keeps it 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?

Usage is implied by the filter list, and there is one useful caveat ('open_now only matches owner-supplied or official-site hours, and none are recorded yet') that effectively tells the agent not to rely on that parameter. However, there is no explicit when-to-use or when-not-to-use guidance versus sibling tools like nearby_places or list_places.

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