device_realtime_correction

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

There are no annotations, so the description carries the full burden. The verb '조회' clearly implies a read-only query, which offers some transparency, but the description does not disclose whether login is required, how current the 'latest' data is, whether the correction computation has side effects, or any rate limits or performance considerations.

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?

A single, well-structured sentence that states the action, scope, and nature of the result. There is no fluff, and the key qualifier '보정 적용값' is included, making it an efficient and front-loaded description.

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?

With zero parameters, the tool is trivially invocable, and the description names the returned data (latest corrected values for all devices). However, because there is no output schema, it does not describe the shape of the return value, and it omits any mention of authentication or preconditions, leaving the context only partially complete.

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 has zero parameters and schema coverage is effectively 100%. Per the rubric, 0 parameters warrants a baseline of 4, and there are no parameter semantics for the description to explain or clarify.

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 '조회한다' (retrieves/queries) with a clear resource: the latest measurement values of all measuring instruments. The qualifier '보정 적용값으로' (as correction-applied values) distinguishes this from siblings like device_realtime and correction_factors, which likely return raw values or correction factors themselves.

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 provides no guidance on when to use this tool versus alternatives. It does not mention sibling tools, conditions, exclusions, or prerequisites such as authentication or site selection. The only usage indication is implicit in the stated purpose.

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