Get Discord channel metadata

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

Annotations already declare read-only, idempotent, and non-destructive behavior. The description adds behavioral context by stating it doesn't fetch messages and that channels are 'allowlisted,' implying access restrictions not covered by annotations.

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 short sentences that are front-loaded with the verb and resource, followed by an exclusion. No filler or repetition.

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's simplicity (one parameter, no output schema) and strong annotations, the description covers the necessary scope: what it returns and what it excludes. It could add examples or clarify 'allowlisted' but is sufficient for basic use.

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 single parameter channelId is self-explanatory from its name, and the description adds minimal constraint by clarifying the channel is 'one allowlisted guild channel.' With no schema description, the description slightly compensates, but doesn't explain ID format or retrieval behavior.

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 uses the specific verb 'Gets' plus resource 'Discord channel metadata', and explicitly distinguishes from message-fetching tools by stating 'This does not fetch messages.' This clearly places it among sibling tools.

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 implies usage for retrieving channel metadata when you need non-message channel info, and the exclusion of messages helps differentiate from discord_get_message. However, it doesn't explicitly name an alternative tool or state when to prefer it over other siblings.

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