get_help_page

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

With no annotations, the description carries the behavioral burden; it implies read-only, single-page scoping ('one page', 'shipped documentation'), which is meaningful. However it does not state the return format, whether an unknown path errors or returns empty, or any other operational behavior beyond scope.

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?

Front-loads the purpose, then usage motivation, then the parameter, with no filler. The example paths are slightly repetitive but each illustrates a distinct namespace, so they earn their 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?

For a one-parameter read tool with no annotations or output schema, the definition covers what the tool returns (doc page content) and how to obtain a valid path. Only the error/empty-path behavior is left unaddressed, which is minor.

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 0% and the schema only titles the field 'Path', so the description must compensate. It does so well by tying path to search_help output and giving concrete format examples ('nodes/sop/scatter', 'vex/functions/noise', 'expressions/ch').

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?

States a specific verb (Fetch) and resource (one page of Houdini's shipped documentation by path), with scope clearly bounded to a single page. It contrasts cleanly with the sibling search_help, which only returns paths rather than content.

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?

Gives concrete when-to-use guidance (before VEX wrangles, before channel expressions) and points to search_help as the source of valid paths. It stops short of explicitly stating when NOT to call it, but the context is clear enough for correct selection.

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