quince_navigation

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

With no annotations, the description carries the disclosure burden. It discloses the full mega-menu contents, example tabs, named subcategory groups, and that every category/link has a browsable slug. It also clarifies the taxonomic relationship to quince-categories. It doesn't mention caching or freshness, but for a static navigation menu that is a minor omission.

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, followed by concrete detail and a differentiating note. The enumeration of example tabs is somewhat long but every element adds specificity about what the menu contains. No filler or redundant phrasing.

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 zero-parameter read-only navigation tool with no output schema, the description is thorough: it names the vendor, the exact dataset, example content, the guarantee that every category/link has a slug, and the relationship to quince-categories. An agent knows exactly what to expect and when to choose 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 input schema has zero parameters and 100% coverage, so there are no parameter semantics to clarify. The description adds context about the returned structure rather than inputs, which is appropriate for a parameterless tool. Baseline 4 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 'Get Quince's header navigation menu,' a specific verb and resource. It enumerates the menu's contents (top-level tabs, subcategory groups, slugs) and explicitly distinguishes itself from quince-categories, making its purpose unambiguous even among the large sibling set.

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 explicitly contrasts with quince-categories: 'navigation is Quince's own curated site structure, while quince-categories reports live per-value product counts.' This tells an agent when to choose this tool over the sibling, and clarifies that this tool provides the nav tree rather than facet data.

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