start_authoring_run

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

With no annotations provided, the description carries full burden. It only states initialization but does not disclose what happens if a run already exists, whether it overwrites, or any side effects. The 'resume_if_exists' and 'force_new' parameters imply behavior, but the description does not clarify them.

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, concise and front-loaded with the action. However, it could be slightly more informative without adding length, so not a 5.

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?

Given the tool's complexity (5 parameters, no annotations, no output schema description) and the presence of closely related sibling tools, the description is incomplete. It lacks guidance on usage, parameter details, and behavioral traits.

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%, so the description must add meaning. It only mentions 'datasource_path' implicitly via 'from an Excel or Hyper datasource', but fails to explain 'output_dir', 'resume_if_exists', 'authoring_mode', or 'force_new'. The default values are in schema but no semantic explanation.

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 uses a specific verb ('Initialize') and identifies the resource ('guided authoring run') and source types ('Excel or Hyper datasource'). However, it doesn't clearly distinguish from sibling tools like 'resume_authoring_run' or 'reopen_authoring_stage', which are closely related.

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 does not provide any guidance on when to use this tool versus alternatives like 'resume_authoring_run' or 'reopen_authoring_stage'. There is no mention of prerequisites or context for use.

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