Browse iNavi Map Examples

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

No annotations are provided, so the description carries full burden. It discloses that returns are lightweight summaries with ID, title, description, and tags, and mentions a 'two-tier metadata system' without elaboration. More detail on the two-tier system would improve transparency, but current info is sufficient for a listing 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 concise with no redundancy. It front-loads the purpose, then immediately provides usage guidance and filtering options. 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 (one optional parameter, output schema exists), the description fully covers usage flow, filtering, and return summary fields. No gaps for an agent to select and invoke 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?

Schema coverage is 100% for the single parameter 'category'. The description adds context by explaining what each enum value represents and clarifies that omitting the parameter returns all examples, adding value 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 clearly states the tool is for browsing and discovering iNavi Maps HTML examples, with specific verb 'browse and discover' and resource 'iNavi Maps HTML examples'. It distinguishes from sibling tool 'get_map_example' by noting it returns summaries for discovery.

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 advises to call this tool first to explore examples, then use 'get_map_example' with a specific ID. Also provides optional filtering by category, giving clear when-to-use and sequential guidance.

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