os_net_station_log

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows the operation is safe and repeatable. The description adds a small amount of context by mentioning 'inline/resource delivery controls', hinting at the delivery mechanism, but it does not explain what these controls do or any side effects. Since annotations cover the core safety profile, a score of 3 is appropriate – the description adds minimal behavioral detail beyond annotations.

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, front-loaded sentence that directly states the purpose without any fluff. It is concise and efficient, with no redundant words. Every word earns its place, making it a model of brevity.

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 4 parameters, 1 required, and 0% schema description coverage, the description is far too sparse. It does not explain the delivery modes, the meaning of inlineMaxBytes, or what the log text contains. Although an output schema exists (which partially offsets the need to explain return values), the agent still lacks enough context to correctly invoke the tool with proper parameter values, especially for the optional delivery parameters.

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 description coverage is 0%, meaning the description must explain the parameters, but it does not. It only mentions 'inline/resource delivery controls', which hints at the 'delivery' parameter, but provides no detail about 'stationId' (required) or 'inlineMaxBytes'. The description does not compensate for the lack of schema descriptions, leaving the agent to guess parameter meanings.

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 states a specific verb ('Get') and a clear resource ('OS Net station log text'), which is unambiguous. It also mentions 'inline/resource delivery controls', giving a hint about the delivery parameter. However, it does not explicitly differentiate from the sibling 'os_net_station_get', which likely retrieves station metadata rather than logs, so the distinction is implied rather than stated.

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 when to choose 'inline' vs 'resource' vs 'auto' delivery, nor does it refer to sibling tools like 'os_net_station_get' or other log-related tools. The usage context is entirely left to the agent to infer from the parameter names and enum values.

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