copypass_run

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

The description mentions storing a run record and echoing operator context, implying some state mutation, but does not disclose side effects, idempotency, or permission requirements. With no annotations provided, the description carries full responsibility for behavioral clarity and falls short.

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 brief (two sentences) but the second sentence is dense and technical ('Chunk 1 stores an in-session run record...'), which may confuse agents. It could be more front-loaded with the core action.

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 no output schema and the description does not explain what the tool returns (e.g., a run ID). It also fails to clarify what 'Chunk 1' refers to, leaving important context unexplained. For a 'start run' action, the agent likely needs to know the result to proceed.

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 100%, so each parameter has a description in the schema. The description adds no additional meaning beyond what the schema already provides, such as the purpose of the 'profile' enum or the significance of 'audience' and 'goal'. Baseline 3 is appropriate.

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 identifies the tool as starting a 'scaffold CopyPass run for AI-generated copy', providing a clear verb and resource. However, the term 'scaffold' and 'Chunk 1' are jargon that may not be immediately clear, and it fails to distinguish this from sibling tools like seopass_run, uxpass_run, or testpass_run, which have similar structures but different domains.

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 is provided on when to use this tool versus alternatives. The description does not specify appropriate contexts or prerequisites, leaving the agent to infer usage from the name alone.

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