github_repos_redeliver_webhook_delivery

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

With no annotations, the description should disclose behavioral traits such as idempotency, side effects, or rate limits. It only states the action without any behavioral context, leaving critical uncertainty about the operation's implications.

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 with no redundant information. It is front-loaded with the action and resource, making it easily scannable.

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?

Despite the tool having 4 required parameters and no output schema, the description does not explain the redelivery process, prerequisites, or expected behavior. It is too minimal to fully equip an agent for correct invocation.

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 100% (all parameters have descriptions), but those descriptions merely repeat parameter names (e.g., 'owner', 'repo'). The description adds no semantic value beyond the schema, meeting the baseline of 3 as per rubric.

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 'Redeliver a delivery for a repository webhook' clearly states the verb (redeliver) and resource (delivery for a repository webhook). However, it does not differentiate from sibling tools like github_apps_redeliver_webhook_delivery or github_orgs_redeliver_webhook_delivery, lacking scope distinction.

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 (e.g., other redelivery endpoints) or when not to use it. The absence of usage context limits an agent's ability to choose correctly.

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