Pause Live Source

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, which the description does not contradict. The description adds minimal extra context by specifying that it pauses 'syncing' rather than deleting or modifying the source, but it does not explain behavioral effects such as whether ongoing syncs are stopped or whether the source remains retrievable until resumed.

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, complete sentence with no filler or redundant phrases. It is front-loaded with the action verb and clearly communicates the tool's purpose, earning every word.

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 low complexity of the tool (two required string parameters, no output schema) and the informative annotations (idempotent, non-destructive), the description is sufficiently complete for an agent to understand and invoke the tool. It clearly states what action is performed, and the lack of details about side effects is compensated by the annotations.

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?

The input schema covers 100% of the parameters, with descriptions 'Knowledge base id' and 'Live source id'. The tool description adds no additional parameter information beyond what the schema already provides, so the baseline score of 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 uses a specific verb phrase 'Pause syncing' and identifies the resource as 'a live source', making the tool's action immediately clear. It distinguishes itself from sibling tools like lyzr_livesource_resume, lyzr_livesource_remove, and lyzr_livesource_sync by specifically targeting the pause 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?

The description implies usage when the user wants to halt syncing for a live source, but it does not explicitly state when to use this tool versus alternatives like resume or remove. No exclusions or context about prerequisites are provided, so guidance is only implied by the verb 'pause'.

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