sync_workflow_improvement_report

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

With no annotations, the description carries the full burden. It usefully discloses that identity is session-derived, that only the evaluator's allow-listed outcome summary is accepted, and that packet implementation is out of scope. However, it does not explain overwrite or idempotency behavior, reversibility, or permission requirements, leaving meaningful gaps for a write operation.

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 compact and front-loaded: the first sentence states the core action, and the second paragraph adds essential constraints without fluff. Every sentence provides distinct value, making it easy for an agent to parse quickly.

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 description covers key auth scoping and acceptance limitations, and an output schema exists to describe return values. However, it does not explain how output_dir relates to the operation or how this tool fits into the broader workflow improvement lifecycle relative to siblings such as run_workflow_improvement_cycle and decide_workflow_improvement_packet. This leaves moderate gaps for an agent orchestrating the full workflow.

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% and the description never mentions the sole parameter output_dir. The agent must infer its purpose from the parameter name and default value alone, which is insufficient for confident invocation. The description should at least clarify whether output_dir points to the local report location or where output is written.

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 a specific action: syncing the latest local evaluator report to an authenticated scoped ledger. It also differentiates this from packet implementation by explicitly noting that a separate immutable human approval decision is required, which distinguishes it from related sibling tools like decide_workflow_improvement_packet.

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 practical usage context: the server derives tenant, company, and actor from the session, so the agent knows not to supply them. It also implies when not to use this tool by stating that packet implementation is a separate step requiring human approval, though it does not explicitly name alternative tools.

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