unifi_get_device_stats

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

No annotations provided, so the description bears full responsibility for behavioral disclosure. It does not state that the operation is read-only, what kind of statistics are returned (e.g., performance metrics), or any required permissions or rate limits. This is insufficient for an agent to understand side effects or constraints.

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 sentence with no wasted words, but it is too brief to be fully informative. It earns high marks for conciseness but not for completeness.

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 has no output schema, so the description should hint at return values (e.g., types of statistics). It does not, leaving the agent unsure of the tool's output format. For a simple 1-param tool, more context on usage and output is needed.

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 100% (device_id described as 'Device ID or MAC address'), so the description adds no additional meaning beyond the schema. Baseline 3 applies as the schema already explains the parameter adequately.

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 action ('Get statistics') and the target ('for a specific device'), distinguishing it from sibling tools like 'unifi_list_devices' (list all) and 'unifi_get_device_details' (details vs stats). However, it does not explicitly differentiate from 'unifi_get_client_stats' for clients.

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 on when to use this tool versus alternatives. Does not specify prerequisites, constraints, or when not to use it. For instance, it could note that this tool is for device statistics, while 'unifi_get_device_details' is for configuration.

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