unifi_get_firewall_rule_details

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

With no annotations, the description must fully disclose behavioral traits. It only says 'Get detailed information' but does not explain what 'detailed' entails, any side effects, or whether the operation is read-only. The lack of detail forces the agent to assume general read behavior without confirmation.

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 succinct sentence with no wasted words. It is front-loaded with the verb and resource. However, it could be slightly improved by including more context without becoming verbose.

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 the simplicity of the tool (one parameter, no output schema), the description is minimally adequate but fails to set expectations about the response format or content. For an agent to correctly interpret the output, additional detail would be beneficial.

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 has 100% coverage with a description for the single parameter. However, the tool description adds no additional meaning beyond the schema, and the parameter description only states the type ('UUID'). Baseline 3 is appropriate as the schema already documents 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 detailed information') and the resource ('a specific firewall policy'), distinguishing it from sibling tools like 'unifi_list_firewall_rules' which returns a list. However, there is a slight inconsistency between the tool name ('firewall_rule') and description ('firewall policy'), which may cause confusion.

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 (e.g., when to get details vs. list all rules). The description does not specify prerequisites or context, leaving the agent to infer usage without explicit support.

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