emu_update_syslog_publisher

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a write operation ('update') but fails to disclose side effects, whether unspecified fields are reset, required permissions, or atomicity. For a mutation tool with zero annotation coverage, this is a significant gap.

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 single sentence is terse but fails to earn its place as it only restates the tool's obvious purpose. For a tool with 12 parameters and no other documentation, more structured or additive content is expected; the brevity reflects under-specification rather than efficient conciseness.

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?

The tool has 12 optional parameters, no output schema, and no annotations. The description provides zero context about the meaning of 'canonical', what configuration aspects are updatable, valid value ranges, or how changes impact other components. This is utterly inadequate for safe, correct invocation of a configuration tool.

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 0%; the description mentions none of the 12 parameters. It adds no meaning beyond the schema property names, leaving agents to guess at semantics for fields like 'intervalMs' or 'transport' without guidance, which is especially problematic given all parameters are optional and no required constraints exist.

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 ('update') and resource ('canonical syslog publisher configuration'), which clearly identifies the action and resource. This distinguishes it from siblings like emu_get_syslog_publisher (read) and emu_update_cdm_publisher (different resource type).

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 when needing to modify syslog publisher settings, but gives no explicit guidance on when to choose this over alternatives. It does not mention that emu_get_syslog_publisher is for reading or how it relates to CDR/CMR publisher updates, leaving the agent to infer the context.

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