hermes_list_projects

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

With no annotations, the description carries the full burden of behavioral disclosure. It clearly indicates a read-only listing operation and the grouping purpose, but it does not describe pagination behavior, ordering, or response format. The page parameter in the schema partially compensates for the pagination gap.

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 consists of two short sentences with no filler. The core action and resource are front-loaded, and the second sentence adds relevant domain context without unnecessary verbosity.

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 very low complexity—one optional pagination parameter and no required inputs—the description plus schema is sufficient for basic invocation. It could mention return shape or when to choose this over sibling list tools, but these omissions are minor for this use case.

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 only parameter, page, is already fully described in the input schema with type, default, minimum, and a description. The tool description adds no additional parameter semantics, and the schema coverage is 100%, so the baseline 3 applies.

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 the action ('List') and the specific resource ('projects'), and adds useful domain context ('in Hermes') plus the meaning of projects ('group related documents together'). This distinguishes it from sibling tools like hermes_list_products and hermes_list_drafts.

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 statement 'Projects group related documents together' implicitly suggests this tool is useful when needing to enumerate project groupings, but it does not explicitly state when to prefer this over alternatives such as hermes_list_products or hermes_search. Usage context is only implied, not explicit.

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