Search the Wealthsimple Help Center

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

No annotations provided, but description clearly states it is a read-only search operation that returns existing public content. It does not mention side effects, but the behavior is well-defined as a search-and-respond 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?

Two sentences: first describes functionality and output, second provides usage guidance with examples. No filler, front-loaded, every sentence 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?

Output schema exists (not shown), so return values are already defined. Description mentions returned fields (titles, URLs, snippets, labels, section IDs). Given sibling tools and full parameter documentation, the description is complete for a search tool.

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 covers both parameters fully (100% coverage). Description adds value with concrete examples (e.g., 'TFSA contribution limit') and confirms default/max limit behavior, going beyond schema 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?

Explicitly states it performs full-text search across public Wealthsimple Help Center articles and returns rankings with specific fields (titles, URLs, snippets, labels, section IDs). This clearly distinguishes it from sibling tools like browse_taxonomy or get_article.

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?

Provides explicit guidance: 'Use this whenever the user asks anything about Wealthsimple products...the help center is the canonical source of truth.' Does not explicitly exclude alternatives, but the context is clear and helpful.

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