service_list

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

The description details the behavior of execution timing and timeout handling, which is useful. However, it does not disclose whether the tool is read-only, what permissions are needed, or any side effects. With no annotations, this leaves a gap in transparency.

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 four sentences long but starts with a tautological phrase. It front-loads timing details rather than the core purpose. It could be more concise and better structured by stating the tool's main action first.

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 the tool has 8 parameters, no schema descriptions, and no annotations, the description is incomplete. It does not mention the output schema or explain three key parameters. The core function is not stated, leaving the agent with significant gaps.

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?

The input schema has 8 parameters with 0% description coverage. The description explains only the execution timing parameters (expected_runtime_seconds, timeout_seconds, check_after_seconds, poll_interval_seconds, on_timeout) but fails to explain the filter parameters: user, limit, and state. This leaves most parameters semantically opaque.

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 starts with 'Kali Agent MCP tool: service_list' which is a tautology, and then focuses entirely on execution timing parameters without stating the core function of listing services. It fails to explicitly describe what the tool does, leaving the purpose unclear.

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 provides guidance on choosing on_timeout values but offers no comparison to sibling tools like service_action, service_logs, or service_status. It does not specify when to use service_list instead of alternatives.

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