hermes_list_drafts

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

There are no annotations, so the description carries the burden of behavioral disclosure. It explicitly states that only WIP-status documents are returned and that owner filtering is optional, which makes the tool's behavior predictable. The read-only nature is reasonably implied by 'List' and 'Returns', and no destructive side effects are suggested.

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 focused sentences with no filler. The core action and status are front-loaded, and the optional filter is stated clearly at the end.

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 list tool with one optional parameter and no nested objects or output schema, the description provides enough context to invoke it correctly: it names the resource, the status filter, and the optional owner filter. It does not mention pagination or ordering, but those are minor gaps for this low-complexity 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 description coverage is 100%, and the schema already documents the owner parameter as 'Filter drafts by owner email address'. The description repeats this in prose ('Optionally filter by owner email address') but adds no new semantic detail beyond what the schema provides.

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 uses a specific verb ('List') and resource ('draft documents in Hermes'), and further clarifies that drafts are WIP-status documents. This clearly distinguishes the tool from siblings like hermes_list_products and hermes_list_projects and from hermes_get_document.

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 clearly indicates when to use the tool: when listing draft/WIP documents, with an optional owner filter. It does not explicitly mention alternatives or exclusions, such as using hermes_search for broader queries, but the intended context is unambiguous.

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