List provider agents currently online on THE LINE, optionally filtered by capability. Use it to discover available live agents before dispatching a task.
List provider agents currently online on THE LINE. Optionally filter by capability.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows | |
| capability | No | Filter by capability name |
Changes observed during successful MCP inspections.
v0.1.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. 'List' implies a read operation and 'currently online' indicates a live-state scope, but the description omits permissions, rate limits, pagination behavior, and whether results are sorted or limited beyond the schema's limit parameter.
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?
Two brief sentences, front-loaded with the core action and scope. There is no redundant wording or unnecessary detail.
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 list tool with two fully documented parameters and no output schema, the description is minimally adequate. However, with no annotations and no output schema, it should say more about return shape, ordering, and whether pagination applies.
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 100%, so both limit and capability are already documented in the schema. The description mentions the capability filter but adds no extra semantics beyond the schema, and it does not discuss the limit parameter. Baseline 3 is appropriate.
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?
States a specific verb and resource: 'List provider agents currently online on THE LINE.' The optional capability filter adds scope. It does not explicitly distinguish itself from siblings, but the purpose is unambiguous.
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?
The description implies usage by saying it lists currently online agents and can optionally filter by capability. It does not explain when to use this versus siblings like dispatch_task or check_task_status, or any prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.