discord_get_channel

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

With no annotations provided, the description alone must carry behavioral disclosure. 'Get details' implies a read-only operation, but the description does not state that it is non-destructive, whether it requires special permissions, or what happens on invalid IDs. It adds very little beyond the tool name.

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 a single short sentence with no filler or redundant content, which makes it concise and easy to parse. However, it is so minimal that it borders on under-specification rather than genuine conciseness, earning a slight penalty.

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?

Given the tool has no annotations and a 0% schema description coverage, the description is far too thin. It does not explain the optional guild_id, does not mention expected output details, and provides no differentiation from related channel tools. An agent would likely need to guess or inspect the schema in detail.

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 description coverage is 0%, so the description must compensate for explaining both parameters. It fails to do so: channel_id is only implied by 'channel', and guild_id is entirely unexplained despite being optional. The description adds no meaning beyond the parameter structure.

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 verb (Get) and resource (details for a guild channel), making the tool's core purpose obvious. However, it does not explicitly differentiate itself from sibling tools like discord_list_channels or discord_get_role, leaving the agent to infer the distinction from the name.

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?

No guidance is given for when to use this tool versus alternatives. There is no mention of needing an existing channel_id, no note about how it differs from listing channels, and no conditions for choosing this over discord_get_member or discord_get_role. The agent is left to infer usage context.

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