getAppControlCategories

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 only that results are scoped per-site; it says nothing about whether the list is paginated, whether it can be large, or how the default site fallback behaves at runtime, leaving little beyond structured data.

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 no filler and no repetition. It is efficient, though the parenthetical '(families)' plus the trailing clause makes it slightly denser than necessary for the amount of information conveyed.

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, read-only, single-optional-parameter lookup with no output schema, the definition gives enough to call the tool correctly and understand what comes back conceptually (category definitions). Slightly more detail on result shape would make it complete, but nothing essential 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?

Schema coverage is 100%, and the siteId property already documents targeting, the OMADA_SITE_ID default, and the listSites discovery hint. The description's 'for a site' merely echoes that, adding no new syntax, format, or behavioral detail about the parameter.

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?

States a specific verb and resource ('Get application control categories (families) for a site') and clarifies what the objects are ('app category definitions used in application control rules'). This separates it from the rules-listing sibling getAppControlRules without naming that sibling explicitly.

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: an agent can infer it is a prerequisite/reference lookup for app control rule configuration. The description never says when to call this versus getAppControlRules or getApplicationControlStatus, and offers no prerequisites or exclusions.

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