List sections within the Wealthsimple Help Center

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

No annotations provided, so the description bears full responsibility for behavioral disclosure. It only mentions optional filtering and the nature of sections, but omits details like pagination, rate limits, or what happens when no sections match.

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 wasted words. The main action is front-loaded ('List sections'), followed by a clear optional filter and examples.

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 presence of an output schema and sibling tools, the description covers the essential aspects: what sections are, the optional filter, and a reference to list_categories. Minor gap: no mention of sorting or response format, but adequate for a simple list operation.

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% and the description adds value by telling agents to obtain category_id via list_categories and giving examples of section names, which aids correct parameter use 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 lists sections and explains they group related articles, with examples like 'TFSA' and 'Crypto deposits'. It distinguishes itself from siblings by mentioning the optional category_id filter.

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 advises passing a category_id from list_categories to scope results, implying a usage sequence. However, it does not explicitly state when not to use this tool or provide direct comparisons with siblings like list_articles or search_help_center.

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