dpdk_statistic

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

The description declares 'read-only', which is a meaningful behavioral trait, and with no annotations present that trait carries the entire disclosure burden. It does not add any other behavioral context, such as whether DPDK must be enabled, whether the stats are cumulative or a snapshot, or what the return payload looks like. For a simple read-only tool this is minimal but not misleading.

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 four words, front-loaded, and contains no filler or redundant phrasing. For a zero-parameter read-only statistics tool, this length is appropriately sized and easy to parse.

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 description is minimally viable: it tells the agent this is a read-only DPDK statistics query with no arguments. It leaves gaps around which statistics are included, when to choose this over show_statistic or sys_app_statistic, and what output to expect, especially since no output schema exists. It is thin but not unusable.

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?

There are zero parameters, and the schema with an empty properties object already exhaustively documents that. The description adds no parameter-level detail, but none are required. The baseline 4 for zero-parameter tools applies.

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 identifies the resource ('DPDK statistics') and the read-only nature of the operation, which makes the intent clear for a zero-parameter query. It lacks an explicit verb like 'show' or 'get', but the noun phrase plus 'read-only' is enough to understand the purpose. It also helps differentiate it from siblings like dpdk_cmdlog, though not from the more generic show_statistic.

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 given about when to use this tool versus alternatives. The description never mentions related siblings like show_statistic, sys_app_statistic, or dpdk_cmdlog, nor any condition that selects this tool. An agent must infer when DPDK statistics are the right choice.

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