unifi_gen_getdevicetagpage

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds nothing beyond that — no mention of how limit/offset pagination behaves, no default page size, and no indication that this is the raw/generated variant of the endpoint.

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?

Very short, so nothing is bloated, but the second half is a provenance pointer ('generated from developer.ui.com/...') that occupies space without helping the agent invoke the tool. The useful content is a single noun phrase with no front-loaded operational detail.

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?

Three undocumented parameters including an opaque 'filter' object, no output schema, and a confusing overlap with a sibling tool — this definition should do considerably more. It gives the agent no basis for constructing a paginated or filtered request.

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 0% for all three parameters, and the 'filter' parameter has an entirely empty schema ({}), so neither the schema nor the description explains what it accepts. The description does not compensate at all; it names no parameters, no formats, and no defaults.

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 ('List Device Tags'), which is clear enough to know what the tool returns. However it makes no attempt to distinguish itself from the sibling unifi_net_list_device_tags, which appears to do the same thing.

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 on when to use this versus unifi_net_list_device_tags, which is a near-identical sibling. The agent is left to guess which of the two tag-listing endpoints to call, and nothing is said about prerequisites or scope.

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