unifi_gen_getispmetrics

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered by structured data. The description adds nothing beyond that – no note on granularity tradeoffs, data freshness, retention windows, or why 5m only pairs with 24h and 1h only with 7d/30d.

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?

It is short and the purpose is front-loaded, but roughly half the text is a generator provenance URL rather than information useful for tool selection. Brevity here reflects under-specification rather than disciplined editing.

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 four-parameter metrics-retrieval tool with no output schema, the description says nothing about what is returned (latency, jitter, packet loss, availability?), units, or per-site vs. aggregate scope. The schema compensates for parameters, but the return-value burden falls entirely on an undocumented description.

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 mutual exclusivity of duration vs. beginTimestamp/endTimestamp and the 5m/1h interval semantics are already documented in the schema. The description adds no additional parameter meaning, which is the baseline-3 case.

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 is essentially the tool name humanized ("Get ISP Metrics") plus a provenance URL. It restates the title rather than explaining what ISP metrics are or what scope is retrieved, and it makes no attempt to separate this from close siblings such as unifi_sm_get_isp_metrics, unifi_sm_query_isp_metrics, or unifi_gen_queryispmetrics.

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?

There is no when-to-use guidance, no exclusions, and no pointer to the several near-duplicate ISP metrics siblings. An agent must infer from the name alone that this is a read of ISP health/performance data.

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