get_channel_format_guide

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

No annotations provided, but the description fully discloses the return format (JSON with features, limitations, prompts) and that it is a read-only query. It does not explicitly state 'no side effects', but the nature is clear.

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?

The description is well-structured with sections (purpose, usage, channel list, args, returns, examples) and front-loaded. However, it is somewhat verbose with the extensive channel format comparisons; could be slightly trimmed.

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?

With an output schema present, the description covers all necessary information: purpose, usage timing, parameter details, return structure, and examples. It fully equips an agent to use the tool effectively.

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 only parameter 'channel' is fully explained: optional, defaults to returning all channels, and a complete list of possible values is provided in the description, compensating for 0% schema description coverage.

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 clearly states the tool retrieves formatting strategy guides for notification channels, including Markdown features, limitations, and best prompts. It distinguishes itself from sibling tools like send_notification by positioning itself as a pre-send helper.

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?

Explicitly states '在调用 send_notification 之前使用此工具' (use before calling send_notification). Provides examples for retrieving all or specific channel guides, making the usage context absolutely clear.

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