line_status

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

The description discloses it creates a read-only snapshot, reports several attributes, and does not return secrets/chat content. It could mention potential side effects (e.g., overwriting previous snapshots), but overall it informs the agent about the tool's non-destructive nature and output.

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 that efficiently conveys purpose, behavior, and usage. Every word serves a purpose, and it is well-structured with no redundancy.

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 no parameters, no output schema, and the tool's simplicity, the description fully covers what the tool does, what it returns, and when to use it. It is complete for the context.

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 tool has zero parameters, so the baseline is 4. The description adds no parameter details, but none are needed. Schema coverage is 100%.

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 specific verbs ('Refresh and verify', 'report') and a clear resource ('local LINE DB snapshot'). It explicitly states what the tool does and what it does not return (secrets/chat content), leaving no ambiguity.

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 says 'Call this before every LINE read task,' providing explicit when-to-use guidance. Since no sibling tools exist, there are no alternatives to differentiate, but the context is clear.

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