get_channel_format_guide

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

无注释，描述承担了行为披露责任。详细列出了各渠道支持的特性，并说明返回JSON格式。虽然未提副作用或权限，但作为只读工具，信息披露充分。

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?

描述较长但结构分明：前导介绍、渠道概览、参数说明、返回值、示例。每个部分都有价值，冗余少，但可以进一步精炼。

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?

有输出schema，描述也说明了返回格式。参数解释彻底，没有遗漏关键信息。对于该工具，描述已足够支持代理正确调用。

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覆盖率为0%，描述完全补偿了参数说明。channel参数的每个可选值都列出，并明确不指定时返回所有策略，语义清晰。

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?

描述明确说明工具获取通知渠道的格式化策略指南，动词+资源清晰，并且列出了各渠道的格式差异，与send_notification等sibling工具区分明显。

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?

明确说明在调用send_notification之前使用，提供了具体使用场景，但没有明确指定替代方案或什么时候不使用。不过该工具是唯一的指南类工具，与sibling区分已足够。

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