alterios_fast_live_write

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

With no annotations, the description carries full burden. It only mentions 'plan or apply' without detailing what these phases entail, whether the tool is destructive, requires approval, or what side effects occur. Parameters like dry_run and require_clean_health imply safety checks, but these are not disclosed in the description.

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 sentence of 12 words, which is concise but insufficient. It lacks the detail needed for a tool with 13 parameters, sacrificing utility for brevity.

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 complex tool with 3 required nested parameters, no annotations, and an output schema, the description is severely incomplete. It does not explain the workflow, parameter usage, or output, leaving the agent ill-equipped to invoke the tool correctly.

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%, yet the description provides no explanation for any parameter. It does not mention required parameters (scenario_tool, scenario_args, etc.) or complex objects like delivery_evidence, leaving the agent without necessary guidance.

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 action (plan or apply) and resource (one approved scenario) within the fast live-write workflow. It distinguishes from bulk write tools in the sibling list, but does not explicitly differentiate from other write tools like alterios_rest_write or alterios_call_write_service.

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?

No guidance on when to use this tool versus alternatives. The description does not mention prerequisites, when not to use, or comparison to sibling tools such as alterios_fast_live_bulk_delete or alterios_rest_write.

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