Retrieve device information in JSON format. Access hardware and software specs for the current system.
[viewer] Device Info
Outputs:
info (json): Info
This tool declares no required parameters. Add optional parameters from the input schema as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {},
"name": "tool_device_info"
}
}| Name | Required | Description | Default |
|---|---|---|---|
| info | No | Info |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden of behavioral disclosure, but it reveals nothing about side effects, permissions, return values, or operational behavior. It only states that it outputs info, which is tautological.
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 extremely short but not concise in a meaningful way—it under-specifies the tool's purpose and parameters. The few words add no value beyond restating the name.
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?
The tool is trivial in parameter count but the description is inadequate: no output schema, no annotations, and no meaningful details about inputs or outputs. It fails to provide a complete picture of the tool's functionality.
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 single parameter 'info' is described only as 'Info' in both schema and description. The description labels it as an output rather than an input, contradicting the schema's definition of an input property, which is misleading.
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?
Description 'Device Info' restates the tool name without specifying an action or what kind of device info is returned. The output section is equally vague, only repeating 'info (json): Info'.
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 or what alternatives exist. The description lacks any context about use cases or exclusions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.