device_get

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description's claim 'Get device details' adds no new behavioral insight. It does not disclose any additional traits such as response size, pagination, or authentication requirements. However, there is no contradiction with 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?

A single concise sentence that is front-loaded with the essential action and resource. No wasted words, and the structure is clear and to the point.

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 presence of an output schema (not shown but indicated) and full parameter coverage, the description is adequate but incomplete. It does not explain what 'details' encompasses, nor does it provide context about when to use this tool over other device-focused tools. It meets the minimum viability.

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 100% description coverage with 'Device hostname' for the only parameter. The description simply says 'by hostname', which reiterates the schema. It adds no extra meaning or usage details beyond what the schema already conveys.

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 clearly states the verb 'Get', the resource 'device details', and the method 'by hostname' from 'LibreNMS'. It effectively distinguishes itself from sibling tools like 'devices_list' (which lists all devices) and 'device_links' or 'device_availability' (which focus on specific aspects).

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, there is no mention that for a specific device's ports or availability, one should use 'device_ports' or 'device_availability' instead. The description only explains what it does, not the context of its use.

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