km_add_pause

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

With no annotations, the description should disclose behavioral traits like whether adding a pause appends to the macro, allows duplicate pauses, or requires specific permissions. The current description only states the action without any such details, leaving the agent uninformed about side effects or dependencies.

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 extremely concise, consisting of one short sentence that directly states the tool's purpose. Every word earns its place; there is no fluff or redundancy. This is a model of conciseness for a simple tool.

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 has no output schema and no annotations, the description should fill gaps about behavior (e.g., what happens if seconds is negative or zero) and return values. It fails to do so, leaving the definition incomplete for an agent to use confidently.

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 coverage is 100% and the schema already provides clear descriptions for both parameters ('Macro name or UID', 'Number of seconds to pause'). The description adds no additional semantic value beyond what the schema offers, meeting the baseline expectation.

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 'Add a pause action to a macro' clearly states the action (add) and resource (pause action to a macro), making the tool's purpose easy to understand. It distinguishes from sibling tools like km_add_calculation or km_add_notification by specifying 'pause', but it does not explicitly differentiate from the generic km_add_action.

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. For example, it does not explain scenarios where adding a pause is preferred over other actions, nor does it mention prerequisites or constraints like the macro must exist.

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