discord_set_channel_position

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

Description adds behavioral info beyond annotations: requires Manage Channels permission, returns confirmation. Annotations already indicate idempotent, non-destructive write operation, so description adds useful detail.

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?

Two sentences with no redundant words. Each sentence provides essential information: purpose, alternative, permission, return. Front-loaded with the core action.

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 a simple tool with well-described params and annotations, this description covers purpose, sibling distinction, permission requirement, and return type. No gaps.

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 good descriptions for both parameters (position as zero-based integer with bounds, channel_id as snowflake pattern). Description does not add extra parameter info, so baseline 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?

Clearly states 'set a channel's display order within its category' which is a specific verb+resource. Distinguishes from sibling 'discord_move_channel' by specifying the alternative for changing category.

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 tells when to use this tool (to set position within category) and points to the alternative tool for changing category. Also notes required permission.

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