List Hermes API docs snapshot sections

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds meaningful context beyond annotations by specifying the output granularity (sections, slugs, provenance, wrapper mapping) and the key behavioral trait that no network call occurs. It complements the annotations rather than repeating them.

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?

A single, information-dense sentence that communicates purpose, resource, scope, and key behavior (offline snapshot access). Zero wasted words. Each element earned 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?

For a zero-parameter, read-only listing tool with full annotation coverage and an output schema, the description is complete. It conveys the provenance and wrapper-mapping outputs, which is useful given no params. It doesn't describe return structure, but an output schema exists to carry that burden.

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 tool has zero parameters, and schema description coverage is 100%. Since there are no parameters to document, the not-applicable baseline of 4 applies. The description appropriately focuses on output characteristics since inputs don't exist to explain.

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 explicitly states the verb 'List' with specific resources: documentation resources, section slugs, snapshot provenance, and planned wrapper mapping. It distinguishes this from sibling tools like hermes_api_docs_read (reads docs) and hermes_kanban_api_docs_list (kanban-specific docs). The 'without network refresh' clarifies this is local snapshot data.

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 described scope (bundled/snapshot, no network refresh) clearly indicates when this tool is appropriate for inspecting local doc snapshots. However, it doesn't explicitly name alternative tools or state when NOT to use it (e.g., when you need live/refreshed docs), leaving some ambiguity for the agent.

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