get_guild_webhooks

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

No annotations are provided, so the description carries full responsibility. It only states 'get a list' without disclosing read-only status, permission requirements (e.g., Manage Webhooks), pagination behavior, or response format. This is insufficient for a tool with no annotation safety signals.

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?

A single concise sentence in Japanese, front-loaded with the action and resource. No filler or redundant information, making it efficient and clear.

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 one-parameter tool with no output schema, the description sufficiently conveys the operation. The term '一覧' implies a list of all webhooks in the guild, which is complete enough for an agent to understand the tool's scope. Minor gap: no detail on response structure, but not critical at this complexity.

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 guildId described as 'Webhook一覧を取得するサーバーのID'. The description adds no further semantic detail beyond what the schema already provides. Baseline 3 is appropriate as no additional value is contributed.

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 '特定のDiscordサーバーのWebhook一覧を取得します' uses a specific verb '取得' and resource 'Webhook一覧', clearly indicating a server-scoped list operation. It distinguishes from sibling tools like get_channel_webhooks (channel-scoped) and get_webhook (single webhook) by explicitly scoping to a guild.

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?

Usage is implied by the phrasing 'a specific Discord server', but no explicit when-to-use or alternatives are mentioned. The tool does not contrast itself with get_channel_webhooks or get_webhook, leaving some ambiguity for an agent deciding between server-level and channel-level webhook queries.

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