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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine value by disclosing the shape of the read (duties plus model, version, skills in one call), though it says nothing about what happens for an unknown or unconfigured agent or about the size of the duties list.

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?

One compact sentence with no filler, and the primary payload (duties) is front-loaded ahead of the secondary fields. The parenthetical is dense but readable; slightly fragmentary grammar keeps it off a 5.

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?

There is no output schema, so the description carries the burden of describing returns, and it does so concretely by naming each field group the caller gets back. Combined with annotations covering the safety profile and a fully documented single parameter, an agent has enough to call this correctly; only the get_agent overlap remains open.

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?

With a single parameter at 100% schema coverage, the schema already defines agent_id including its pattern and an example with a pointer to get_account. The description adds no meaning beyond that, which is the expected baseline when the schema does the work.

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 enumerates the returned content (duties with schedule, next run, setter; model; Hermes version; skills), so the resource is identifiable, but it is a noun phrase with no verb and no differentiation from the sibling get_agent, which plausibly returns overlapping agent information. An agent cannot tell from this text alone which of the two to call.

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?

There is no when-to-use guidance at all — nothing says to prefer this over get_agent when you need duty/schedule data, and nothing about prerequisites or when the information is stale. The only routing hint in the whole definition lives in the schema's agent_id description pointing at get_account, not in the description.

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