hermes_operator_recover

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

Highlights 'Dry-run by default', which is a key behavioral trait indicating safety. However, without annotations, more detail is needed, such as the effect of setting 'apply' to true or any side effects.

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?

Very short at two sentences, front-loaded with purpose and key detail. But it is too terse, missing important information that could be added without much length.

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?

Despite having an output schema, the description fails to explain what the tool does in sufficient detail, how to use the parameters, or the overall recovery process. Leaves many questions unanswered.

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 0%. The description only hints at the 'apply' parameter via 'dry-run by default', but does not explain 'profile' or the exact meaning of 'apply'.

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?

Description states 'Conservative recovery sequence' which indicates a recovery operation, but does not specify what resource or system it recovers. It distinguishes from sibling tools by being a recovery tool, but lacks specificity.

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?

No guidance on when to use this tool versus alternatives like hermes_operator_doctor or hermes_operator_snapshot. The description does not mention context or exclusions.

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