set_syslog_target

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that dry_run is the default and that changes are validated against the FortiGate schema, and it indicates the slot is enabled. However, it does not state permission requirements, persistence, or the effect of disabling a slot.

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 front-loaded with the core purpose and then adds only operationally relevant detail about modes, TLS, validation, and dry_run. Every clause earns its place, and there is no filler.

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 an eight-parameter configuration mutation with no annotations and no output schema, the description covers the important behavioral settings: slot, server, port, transport, TLS, and dry_run. It omits vdom and disable, but the schema documents those fully, so the description 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?

Schema description coverage is 100%, so the schema already documents all eight parameters. The description adds cross-parameter context such as reliable mode plus enc_algorithm adding TLS, but most of its parameter detail duplicates the schema. It does not mention vdom or disable.

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 states a specific verb and resource: 'sets server, port and transport on one of the four syslog slots and enables it.' It clearly identifies the tool as a syslog-target configuration operation. It does not explicitly differentiate from siblings such as get_log_targets, so it stops short of a 5.

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?

Usage is implied by the purpose: configure and enable a syslog target. The description mentions default behavior (dry_run, udp) and transport choices, but gives no explicit when-to-use guidance, prerequisites, or alternatives to consider.

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