set_ip_service_enabled

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

The description discloses the tool's state-changing nature and required write permission. No annotations exist, but the description adequately conveys the behavioral impact without hidden side effects.

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 extremely concise, with two sentences plus parameter formatting. No unnecessary words, and the main action is front-loaded.

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 tool with two required params and no output schema, the description covers all essential aspects: purpose, parameters, precondition. No gaps remain for effective use.

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 description adds significant meaning beyond the schema: 'service_id' is explained as '.id or name' with reference to 'ip_services', and 'enabled' is clearly defined as True/False action. Schema coverage was 0%, so this is highly valuable.

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 clearly states the verb 'enable/disable' and resource 'IP service' with an example (telnet/ftp). It distinguishes itself from read-only siblings like 'ip_services' by indicating a write operation.

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 a clear use case (enable/disable IP service) and a prerequisite (MIKROCLAW_ALLOW_WRITE=true). However, it does not explicitly mention alternative tools for list-only operations.

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