hermes_release_doctor

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

No annotations provided, so description must carry full burden. It doesn't disclose side effects (likely read-only but not stated), permissions, or what happens during the check. Vague behavioral context.

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 a single sentence, but it's under-specified. It's concise but lacks necessary detail, making it less useful.

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 no schema descriptions, no annotations, and an output schema that we don't see, the description is incomplete. It doesn't mention return values or behavior, and the parameters are unexplained.

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 coverage is 0% (no descriptions), and the description doesn't explain the three parameters (timeout, workdir, full_tests). Their purpose and impact are not clarified, so the description adds no value beyond parameter names.

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 the tool checks release safety for repo/operator, which is specific enough. However, it lacks detail on what 'safe to ship' entails, and doesn't distinguish from similar sibling tools like hermes_operator_doctor.

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 vs alternatives (e.g., hermes_operator_doctor). The description implies it's for release readiness, but no explicit when/when-not or prerequisites.

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