Get Igmp Proxy Config

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds nothing beyond that: no note on whether IGMP proxy requires enabling elsewhere, what privilege level is needed, or what the config pertains to. A single restated phrase adds no behavioral context.

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?

One short, front-loaded phrase with zero waste. It is efficient, though its brevity borders on under-specification rather than true conciseness given the absence of any supplementary context.

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?

An output schema exists, so return values need no explanation, and a zero-parameter read-only getter is a simple tool. Even so, for a feature like IGMP proxy that is not obviously placed in the sibling inventory, a brief note on scope or prerequisites would round it out; the definition is minimally adequate.

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?

The tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify about inputs, and the empty schema with additionalProperties=false is self-explanatory.

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 gives a clear verb+resource ('获取 IGMP 代理配置' = get IGMP proxy configuration), which is specific and unambiguous. However it offers no differentiation from the adjacent config getters in the sibling list (e.g. get_udp_proxy_config, get_iptv_config), so it is clear but not distinguishing.

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 guidance on when to call this tool, what context it applies to, or how it relates to alternatives such as get_udp_proxy_config or the proxy dial account tools. The agent must infer usage purely from the name.

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