github_repos_get_webhook_config_for_repo

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

With no annotations, the description must disclose behavioral traits. It only states 'Get', implying a read operation, but does not mention required permissions, rate limits, error conditions, or whether the output includes full config details. This is insufficient for a mutation-free read tool.

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 concise at 8 words, but it is under-specified. While no words are wasted, more detail would improve clarity. It is not a tautology, but it barely exceeds minimal functionality.

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 no output schema and no annotations, the description should explain what a 'webhook configuration' is and what the return value contains. The tool has three required parameters, but the description does not elaborate on how they are used or any constraints. This is incomplete for reliable agent usage.

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 has 100% coverage with each parameter described only by its name (e.g., 'owner'). The description does not add any additional meaning or context for the parameters, so it meets the baseline expectation but does not improve understanding.

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 tool retrieves a webhook configuration for a repository. The verb 'Get' and resource 'webhook configuration' are specific. However, it does not differentiate from sibling tools like github_repos_get_webhook (which might return the webhook object) or github_repos_get_webhook_delivery, leaving ambiguity about when to use each.

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 provided on when to use this tool versus alternatives. For example, it does not explain when to retrieve the configuration versus the webhook itself, or what prerequisites are needed (e.g., admin permissions).

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