Get Preset Details

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

No annotations are provided, so the description carries the burden. It lists all returned information categories (tags, fields, geometry types, parent/child), sufficiently disclosing what to expect. No contradictions.

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 the main purpose, then explains presets, then lists what is returned, then usage. It is slightly verbose but well-structured and informative without 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?

Given no output schema, the description adequately covers return values (tags, fields, geometry types, parent/child). It might miss mentioning any pagination or error conditions, but for a simple retrieval tool it is mostly 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 coverage is 100% (baseline 3). The description adds value by explaining the preset ID pattern (key/value) and giving examples (e.g., 'amenity/restaurant'), and referencing search_presets for finding IDs. This goes beyond simple 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 tool retrieves detailed information about an OpenStreetMap preset, explains what a preset is, and lists the comprehensive information returned. It distinguishes from siblings like search_presets (which finds IDs) by focusing on details retrieval.

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 use cases: understanding tagging, learning available fields, getting example values. It implicitly contrasts with search_presets for finding IDs but does not explicitly state when not to use or list alternatives beyond the sibling tools context.

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