getUrlFilterBlacklist

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 that results are paginated and that returned values are MAC addresses blocked from network access, which is genuine value beyond the annotations, but it says nothing about max page behavior, empty-result semantics, or permissions.

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?

Two short sentences, front-loaded with the verb and resource, followed by a single clarifying sentence on return content. No filler, no restatement of the tool name.

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, zero-required-parameter list tool with a fully documented schema and no output schema, the description supplies enough to call it correctly and to know roughly what comes back. The only missing piece is routing among closely related filter/ACL siblings.

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%, including the siteId fallback to OMADA_SITE_ID and the 1–1000 pageSize bounds, so the schema already carries the parameter semantics. The description only restates 'for a site (paginated)' and adds no format or default-override detail beyond what is documented.

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 ('Get') and resource ('MAC-based deny/blacklist filter entries for a site'), and explicitly clarifies that the entries are MAC addresses rather than URL patterns, which disambiguates it from the URL-filter siblings despite the tool's name. It never names getUrlFilterWhitelist, getUrlFilterRules, or getMacFilterDetail directly, so sibling differentiation is implicit rather than stated.

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?

The phrase 'for a site' and '(paginated)' imply the context of listing deny entries within a site scope, but there is no explicit when-to-use or when-not-to-use guidance. Nothing tells the agent whether to prefer this over getMacFilterDetail or getUrlFilterRules when both appear relevant.

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