List Ennodia harnesses

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

Annotations already declare it read-only and local, so the safety profile is covered; the description adds the discovery-cache behavior (refresh re-scans), the caveat that model capabilities do not guarantee native input through a harness, and a troubleshooting-first role. It does not describe pagination or the shape of the returned 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?

Front-loads the action and returned facets, then layers the two directives. Dense and telegraphic but every clause carries information; no filler sentences.

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?

No output schema exists, yet the description enumerates what discovery yields (availability, versions, capabilities, adapter notes, inputGuidance), which compensates. For a single-optional-param read tool with annotations covering safety, this is close to complete.

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?

Only one parameter and schema coverage is 100%, so the schema fully documents refresh. The description adds no format or semantic detail about it, 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?

Names a specific verb (Discover) and resource (local harnesses) and enumerates the returned facets: availability, versions, capabilities, adapter notes, inputGuidance. It is clearly distinguishable from ennodia_list_skills, though it never explicitly contrasts itself with that sibling.

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?

Gives concrete usage context: read inputGuidance before audio/image/video work, and use this first when setup or routing fails. It states when to reach for the tool but names no alternative sibling to prefer instead.

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