discord_follow_announcement_channel

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

The description discloses that the tool creates a subscription (mutating), requires specific permissions, and returns a confirmation. It adds value beyond annotations by explaining the effect and permission requirement. It could further detail error cases or rate limits.

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 concise (two sentences), front-loaded with the main verb 'Subscribe', and every sentence adds essential information without 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?

For its complexity, the description covers the main aspects: action, constraints, permission, and return. It could clarify that the target channel must be a text channel, but overall it is sufficiently complete for an agent.

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% with clear parameter descriptions. The tool description does not add additional semantic information beyond what the schema provides, so baseline score of 3 is appropriate.

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 action ('Subscribe a target channel to an announcement channel'), identifies the specific resources (source and target channels), and explicitly distinguishes from sibling tools like discord_crosspost_message by focusing on following rather than publishing.

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?

The description provides explicit conditions: the source must be an announcement channel, and the Manage Webhooks permission is required in the target. While it does not mention alternatives or when not to use, these conditions effectively guide usage.

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