Fetch the full body of a Wealthsimple Help Center article

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

No annotations are provided, so the description must disclose behavior. It explains the default output format and alternatives, including that HTML is stripped. For a read-only fetch tool, this is adequate. It does not discuss error handling or authentication, but these are not critical for a simple fetch.

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 long, front-loading the main purpose in the first sentence. Every sentence provides essential information without redundancy. It is efficiently structured for quick comprehension.

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 tool's simplicity (2 parameters, 1 required, output schema provided), the description is complete. It explains default behavior, format options, and how to get the article_id. No additional context is necessary for correct invocation.

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% with descriptions for both parameters. The description adds value beyond schema by specifying how to obtain article_id ('via search_help_center or list_articles') and explicitly stating the default format. This helps an agent understand parameter usage.

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 'Fetch the full content of one article,' which is a specific verb-resource combination. It is distinct from sibling tools that browse taxonomy, list articles/categories/sections, resolve URLs, or search. The mention of 'clean Markdown rendering' and format options further clarifies the exact output.

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 provides clear guidance on format usage: default Markdown vs. raw HTML or text. It implies the tool is used after obtaining an article_id via search_help_center or list_articles. However, it does not explicitly state when not to use it or exclusions; the context of sibling tools helps, but direct exclusion is missing.

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