unifi_list_dpi_applications

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states the tool lists applications but doesn't disclose whether this is a read-only operation, requires authentication, has rate limits, returns paginated results, or what format the output takes. The description lacks details on performance, side effects, or error conditions that would help an agent use it correctly.

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, efficient sentence with no wasted words. It front-loads the core purpose ('List all DPI applications') and adds context ('for traffic identification and filtering') that clarifies the domain. Every part of the sentence contributes meaning, making it appropriately concise and well-structured.

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 no annotations and no output schema, the description is incomplete for a tool with 3 parameters. It lacks behavioral context (e.g., read-only nature, pagination behavior implied by offset/limit), output format details, and usage guidelines. While the schema covers parameters well, the description doesn't provide enough information for an agent to fully understand how to invoke and interpret results from this tool.

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%, with all parameters (offset, limit, filter) well-documented in the schema. The description adds no additional parameter semantics beyond implying filtering capability through 'traffic identification and filtering'. Since the schema already fully describes parameters, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't detract.

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 ('List') and resource ('all DPI applications') with a purpose ('for traffic identification and filtering'). It distinguishes from siblings like 'unifi_list_dpi_categories' by specifying applications rather than categories, but doesn't explicitly contrast with other list tools like 'unifi_list_acl_rules' or 'unifi_list_traffic_matching_lists' that might overlap in network management context.

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. The description doesn't mention prerequisites (e.g., needing DPI enabled), exclusions, or comparisons to similar tools like 'unifi_list_traffic_matching_lists' or 'unifi_get_acl_rule' that might serve related purposes in network filtering. Usage is implied only by the tool name and description.

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