get_section_articles

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

With no annotations provided, the description carries the full behavioral burden. It discloses the default TOC behavior, the include_body switch, the max_articles cap, and force_refresh cache bypass. It does not mention auth, rate limits, or error behavior, but it clearly conveys the important behavioral traits that would change how an agent calls the 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 compact and well-structured: two brief sentences establish purpose and workflow, followed by a tight Args list. The Args list is justified because the schema provides no parameter descriptions, and every line in the description adds necessary information without fluff.

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 tool with six parameters and an output schema, the description covers all required and optional parameters, gives defaults, explains the cache behavior, and connects this tool to its siblings. An agent has enough information to call it correctly without needing to inspect sibling schemas or infer hidden prerequisites.

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 parameter explanations in the description are essential. Every parameter gets a meaningful explanation: subdomain is the Help Center hostname, section_id comes from list_sections, locale is an optional filter, include_body controls full article bodies, max_articles limits bodies, and force_refresh bypasses the cache. This fully compensates for the schema's lack of descriptions.

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 the specific action, 'Fetch articles in a section,' and immediately clarifies the default output ('Returns TOC by default') versus the full-text mode. It also creates clear separation from siblings by telling the agent to use article IDs from the TOC with get_article or get_articles, so the tool's role in the workflow is unambiguous.

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 routes the agent through the workflow: 'Use section IDs from list_sections' before calling this tool, and 'Use article IDs from the TOC with get_article or get_articles' after. This names the relevant sibling tools and tells the agent where this tool sits relative to them, which is exactly the usage guidance needed.

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