get_dfw_rule_stats

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds valuable context beyond annotations: returns a flat object not an envelope, lists the exact fields returned, notes counters are cumulative, and warns that new rules may read zero. No contradiction with annotations.

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?

Concise and well-structured: starts with a [READ] tag and clear purpose, then a compact paragraph of usage and return details, followed by an Args list. Every sentence provides useful information without waste.

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 3-parameter read tool with no output schema, the description is complete. It describes the return format (flat object with field names), explains counter behavior, specifies where IDs come from, and includes parameter semantics. No critical information is missing.

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?

With 0% schema description coverage, the description compensates by giving one-line meanings for each parameter: policy_id as parent policy, rule_id as rule identifier, and target as optional NSX Manager target from config. This adds meaning beyond the bare schema titles, though not deeply detailed.

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?

Clearly states it gets packet/byte hit-count statistics for a DFW rule, using a specific verb and resource. Distinguishes itself from sibling tools by explicitly noting it should be used before update_dfw_rule or delete_dfw_rule and that IDs come from list_dfw_rules.

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?

Provides explicit usage context: 'Use it before update_dfw_rule or delete_dfw_rule to see if a rule still matches traffic' and explains counter semantics (cumulative, may read zero on new rule). This gives clear when-to-use guidance despite not enumerating exclusions.

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