getSitesApsBridge

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 externally. The description adds nothing further — no indication of what the bridge config contains, whether it can be empty, or what errors occur for an AP without bridging enabled.

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 short sentence with the resource front-loaded and no redundant wording. It is efficient, though its brevity borders on under-specification rather than optimal tightness.

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?

There is no output schema, so the description is the only place to explain what 'P2P bridge config' returns, yet it does not. For a simple read tool with fully documented params this is not fatal, but the undefined jargon leaves an agent unable to predict the shape or content of the result.

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%: apMac has a pattern and example plus a pointer to listDevices, and siteId documents the OMADA_SITE_ID default and listSites. The description contributes no extra parameter meaning, so the baseline 3 applies.

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 concrete verb ('Get') and a specific sub-resource ('P2P bridge config for an AP'), which distinguishes it from generic AP getters like getApDetail or getApUplinkConfig in the sibling list. It stops short of naming a sibling, but the resource is narrow and identifiable.

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 the many other AP config getters (getApVlanConfig, getApQosConfig, etc.), and no prerequisites or exclusions are mentioned. The agent must infer usage purely from the resource name.

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