list_sections

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

With no annotations, the description carries the behavioral burden. It discloses cache behavior via 'force_refresh: Bypass cache and fetch fresh data' and clarifies that category_id and locale are optional filters. However, it does not mention pagination, list ordering, rate limits, or error behavior for an invalid subdomain, which are relevant unknowns for a list operation.

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 one-line summary is front-loaded, followed by a two-sentence workflow hint and a compact Args block, with no filler. The only minor redundancy is that the optional category filter appears in both the summary and the Args list, which is acceptable for readability.

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?

The description covers the core invocation requirements: what is listed, the optional filters, the cache flag, and the surrounding workflow (list_categories → list_sections → get_section_articles). An output schema exists to describe return values, though pagination and rate-limit behavior are still unaddressed.

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 description coverage is 0%, so the description must compensate — and it does, explaining all four parameters: subdomain as a hostname, category_id with provenance ('from list_categories'), locale as a filter, and force_refresh's cache semantics. Each entry adds meaning beyond the bare schema types, though entries like 'Optional locale filter' are terse.

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 a specific verb+resource: 'List sections in a Help Center, optionally filtered to a category.' It names the data source (Help Center), the resource (sections), and the optional filter, and its workflow hints ('Use category IDs from list_categories') distinguish it from the siblings list_categories and get_section_articles.

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 an explicit data-flow chain: category IDs come from list_categories and section IDs feed into get_section_articles, which tells an agent exactly where this tool sits in the workflow. It does not state explicit when-not-to-use conditions or name alternatives to prefer, so it stops short of a 5.

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