emu_publish_cdr

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

No annotations are provided, so the description must carry the burden of behavioral disclosure. 'Flush' strongly implies a destructive or state-changing operation (clearing a buffer), but it doesn't state what consequences this has — e.g., whether pending CDRs are discarded or moved elsewhere, whether it affects emu_get_cdr_history, or what the operation result means (success, errors). For a state-advancing tool, this leaves the agent blind.

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 a single short sentence with no filler. It front-loads the key verb ('Flush') and target ('the CDR publisher'). Nothing is wasted.

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 zero-parameter tool with no output schema, the description is reasonably complete: the operation (flush publisher) is stated and there are no inputs or outputs to elaborate. However, given the destructive nature of 'flush' and the existence of related publisher tools (emu_publish_cmr, emu_publish_syslog) and history tools (emu_get_cdr_history, emu_list_cdr_records), a note on what the flush actually affects would make it more complete. The absence of annotation safety hints makes the missing behavioral note more significant than it would otherwise be.

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 tool has zero parameters and schema coverage is 100%, so the description has nothing to add about parameter semantics — and 0 parameters means this dimension is trivial. The baseline for a 0-param tool is 4, and no additional parameter-specific burden applies.

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 'Flush the CDR publisher immediately' conveys a specific action (flush) on a specific resource (CDR publisher), but it doesn't distinguish it from sibling tools such as emu_publish_cmr and emu_publish_syslog, which likely operate identically on different publishers. The intent is understandable but the differentiation from related publishing/flushing tools is weak.

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 phrase 'immediately' implies a sense of urgency or a forced flush, and the verb 'flush' suggests discarding a buffer rather than generating new data, but no explicit when-to-use or when-not-to-use guidance is given. The description doesn't mention alternatives like emu_generate_cdrs (for generating) or emu_publish_cmr/emu_publish_syslog (for other publishers), leaving the agent to infer use cases.

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