get_webhook

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that it gets details, without mentioning required permissions, error behavior (e.g., 404 if not found), or the content of the response. This is a minimal disclosure that adds little beyond the tool's 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, concise sentence that front-loads the action (get) and target (specific Discord webhook). It contains no filler or redundant information, earning its place.

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?

The tool is simple with one parameter fully described in the schema, but there is no output schema and the description does not explain what 'detailed information' includes. It vaguely describes the return value, leaving a gap in completeness for users who need to know what fields to expect.

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 input schema provides a description for webhookId ('ID of the webhook to get details for'), achieving 100% schema coverage. The tool description adds no additional parameter semantics, so the 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 it retrieves detailed information for a specific Discord Webhook, using the Japanese verb '取得します' (get/retrieve) and the noun '詳細情報' (detailed information). The word '特定の' (specific) distinguishes it from sibling tools like get_guild_webhooks and get_channel_webhooks, which list webhooks.

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 the use case: fetch details for a single webhook by ID. However, it does not explicitly mention when to use this tool versus the listing endpoints (get_guild_webhooks, get_channel_webhooks) or provide any exclusion criteria. The guidance is implicit rather than explicit.

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