fetch

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

With no annotations, the description carries the behavioral disclosure burden. It discloses that the tool returns the full page in Markdown, that pages can be large, and that multiple id formats are accepted. This is strong coverage for a one-parameter fetch tool, though it could mention failure behavior for invalid ids.

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 compact: three sentences covering function, accepted inputs, and usage caveat. The primary purpose is front-loaded, and every sentence earns its place without meaningless filler.

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 simple one-parameter tool with no annotations and no output schema, the description is complete: it tells the agent what is returned, what id forms are accepted, and when to prefer this tool over search. Nothing essential is missing 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?

The schema already documents 'id' with 100% coverage, so the baseline is 3. The description adds meaningful value by clarifying that 'id' can be a page path, a fragment path with #N, or a full URL — the full-URL variant is not present in the schema description.

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 states a specific action and resource: returning an entire Hermes Agent documentation page in Markdown. It also distinguishes itself from the sibling 'search' by returning full pages rather than fragments, and the id formats make the tool's scope immediately clear.

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 when to use this tool: only when search snippets are insufficient, and not for every search result. It names 'search' as the source of ids and as the lighter-weight alternative, providing clear selection criteria.

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