scope_arm

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

Discloses that it starts waiting for a trigger event and mentions SCPI transport. However, no annotations exist and description lacks details on preconditions, state behavior, or whether it can be called multiple times.

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?

Three short sentences, front-loaded with purpose, no wasted words. Efficiently conveys the core action and follow-up.

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?

Covers the action, follow-up step, and transport protocol. Lacks precondition details (e.g., connection required, trigger configured), but overall sufficient for a simple tool.

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?

No parameters present, so schema coverage is 100%. The description adds no parameter info, which is acceptable given zero parameters; baseline for 0 params is 4.

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?

Clearly states the tool arms the trigger and starts waiting for a trigger event. Distinguishes from siblings like force_trigger and configure_trigger.

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?

Explicitly tells the user to poll with scope_get_acquisition_status for completion. Provides a clear workflow step, though does not state when not to use it.

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