getAppControlRules

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful domain context that these are application-level firewall rules with allow/block semantics, but says nothing about pagination behavior or the shape of the returned rule set.

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?

A single front-loaded sentence with the resource named first and its meaning appended as a clause; there is no filler or repetition.

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?

With no output schema and a list-style response, the description could say more about what a rule object contains or how pagination totals are returned. For a simple, read-only, fully documented-schema list tool it is adequate but thin on return-value context.

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%, so the page, pageSize, and siteId semantics (including the OMADA_SITE_ID fallback and listSites hint) are already fully documented in the schema. The description adds no parameter meaning beyond that, which is the expected baseline at full coverage.

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 states a specific verb and resource ('Get application control rules for a site') and explains what those rules are: application-level firewall rules that allow or block apps or app categories. This distinguishes it from the closely named siblings getAppControlCategories and getAppControlStatus, though it doesn't explicitly name them.

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?

Usage is only implied by the resource being listed; there is no explicit statement of when to prefer this tool over getAppControlCategories, getFirewallSetting, or getUrlFilterRules, and no prerequisites or exclusions are given.

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