apple_maps_guides

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

No annotations are present, so the description carries the burden. It states it 'browse' and 'returns' the home page, which implies read-only, and details the exact payload fields. It does not explicitly assert that no side effects occur, but a browse/returns verb plus no mutation wording is acceptable for a simple fetch 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 front-loaded with purpose and scope, then enumerates returned sections and nested fields. The last sentence is long but conveys guide/publisher structure that is genuinely useful. It is verbose but every part 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?

Given no output schema, the description compensates by detailing what sections appear and the fields each guide/publisher carries. It does not mention pagination or response surface details, but for a home page listing endpoint this is sufficient for an agent to call it 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?

The input schema already describes all three parameters clearly with BCP-47, default lang, city_id source endpoint, and omit-for-Worldwide semantics. The description reinforces the worldwide-or-city distinction but adds virtually no new parameter-level meaning. Higher baseline applies with 100% schema_description_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 uses a specific verb+resource: 'Browse the Apple Guides home page worldwide or for one city' and enumerates its exact sections (featured guide, carousels, city shortcut list, publisher list). It clearly differentiates from apple_maps_guide (singular guide) and apple_maps_guides_cities (city list) by scope.

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 clear context: pass city_id for a city; omit for Worldwide. It also references the /apple-maps/guides/cities endpoint. However, it never names an alternative like apple_maps_guide for single guide details, so it stops short of explicit when-not guidance.

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