synology_system_info

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

With no annotations, the description carries full weight for behavioral disclosure. It implies a read-only operation via the verb 'Get' and lists sample response attributes, which provides some context. However, it does not mention error handling, required permissions, or any side effects (though none are obvious for a system info tool). This is a minimal but acceptable disclosure for a simple getter.

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 conveys the essential purpose and example return fields. It is concise, free of fluff, and every word earns its place. No restructuring or trimming is needed.

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?

For a simple, read-only tool with one parameter and no output schema, the description gives enough context to understand what the tool does and what it returns (model, DSM version, uptime). It does not describe the full return structure or any additional fields, but the examples serve as a sufficient guide. The lack of annotations and output schema is mitigated by the simplicity of the operation.

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 fully documents the only parameter (device_id) with a clear description, achieving 100% schema coverage. The tool description adds no additional semantic detail about the parameter (e.g., format, required permissions), so it does not improve upon the schema. Baseline of 3 applies because the schema does the heavy lifting.

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 ('Get') and identifies a concrete resource ('Synology NAS system information'), and enumerates example fields (model, DSM version, uptime). This clearly distinguishes it as a general system info tool among the sibling tools, including synology_system_utilization which likely focuses on performance metrics.

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 explicit guidance on when to use this tool versus alternatives such as synology_get_network or synology_system_utilization. There is no mention of use cases, prerequisites, or exclusions; usage is only implicitly inferred from the tool name and general description.

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