List articles in a Wealthsimple Help Center section

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

The description discloses that the tool returns only summaries and no body content, which is a key behavioral trait. It implies a read-only operation, which is consistent with no annotations provided. Additional details like ordering or pagination could further improve transparency, but the current disclosure is strong.

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 consists of two efficient sentences, each serving a distinct purpose: stating the tool's output and providing workflow context. No redundant or extraneous words.

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 (context signal), the description appropriately focuses on usage context and scope. It explains the relationship to sibling tools and the intended workflow, making it complete for an agent to use effectively.

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 100%, with both parameters fully described in the schema. The description does not add new semantic information beyond the schema, so a baseline score of 3 is appropriate.

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 it returns article summaries without the body, and it specifies the scope as 'inside a single section'. It also distinguishes itself from siblings by referencing `list_sections` and `get_article` in the workflow.

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 tells the agent to 'Use after list_sections to discover specific articles, then call get_article for full content'. This provides clear when-to-use and next-step guidance, differentiating it from sibling tools like `browse_taxonomy` and `search_help_center`.

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