ligolo_agents_list

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

The description uses the word 'List', which implies a read-only operation, but it does not explicitly state whether there are side effects or permissions required. With no annotations, the description carries the burden and is adequate but not elaborate.

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, clear, and front-loaded sentence with no extraneous information, effectively conveying the tool's purpose.

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?

For a simple parameterless tool with no output schema, the description provides complete context: it lists all connected agents. No further details are needed.

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?

There are no parameters, and the schema description coverage is 100%. The description adds value by explaining the tool's action, which is sufficient given no parameters.

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 'List all connected agents to the ligolo-ng proxy' clearly specifies the verb (List) and the resource (connected agents), and it distinguishes from sibling tools like ligolo_agent_command or ligolo_agent_info by focusing on listing all agents.

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 explicit usage guidance is provided; the tool's purpose is implied by its name and description, but there is no mention of when to use it versus alternatives like ligolo_agent_info for specific agent details.

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