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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=true, covering the safety profile. The description adds that the data is sourced from the navigation menu, implying it's the authoritative source and may change as the site does (consistent with openWorldHint). It doesn't contradict annotations. It adds minimal but useful context beyond annotations.

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 sentences with no redundancy. The primary purpose is front-loaded, and the reference to the sibling tools adds practical context without extra fluff. It 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?

For a parameterless, read-only list tool, the description is complete: it states what is returned (category tree with category_path) and how it relates to the sibling tools. The lack of an output schema is mitigated by the description's clarity. There is nothing an agent needs to know to call it correctly that is missing.

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?

There are no parameters, so the schema coverage is trivially 100%. The description correctly doesn't mention parameters, and the baseline of 4 applies. No additional parameter information is needed.

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 states a specific verb ('List'), a specific resource (Troostwijk Auctions' category tree), and explicitly names the sibling tools that consume the category_path. It clearly distinguishes this from the search and comparison tools by indicating it provides the input needed for them. This is a clear, non-tautological purpose.

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 when to use this tool: before using troostwijk_search_lots or troostwijk_sold_comps, to obtain the category_path values. It doesn't explicitly state 'use this when you need categories' but the reference to the siblings makes it clear. It doesn't mention any exclusions or alternatives beyond the siblings, but that's sufficient for a simple utility tool.

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