gitee_get_webhook

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

No annotations are provided, so the description must convey behavioral traits. It only states 'Get', implying a read-only operation, but does not disclose permission requirements, rate limits, or what happens if the webhook does not exist. The lack of detail leaves the agent uninformed about potential side effects or restrictions.

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 extremely concise (3 words), which is not necessarily a virtue as it sacrifices clarity. It is not front-loaded with key distinguishing information. While it wastes no words, it also fails to provide enough context, so conciseness is a net negative here.

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 complexity of the domain (many sibling tools) and the lack of an output schema, the description should explain what the tool returns or how the response looks. It does not, and the tool is incomplete for an agent to use confidently without external documentation.

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 for parameters (owner, repo, id) with descriptions in the schema. The description 'Get a webhook' adds no additional semantic meaning beyond what the schema provides. Baseline of 3 is appropriate since the schema does the heavy lifting.

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 'Get a webhook' clearly states the action (get) and the resource (webhook). However, it does not differentiate from sibling tools like 'gitee_list_webhooks' which also retrieves webhooks, albeit multiple. The specific identifying parameters (owner, repo, id) are implied by the schema but not mentioned.

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, such as listing webhooks first or updating/deleting. There is no mention that the webhook ID is required or how to obtain it. The description lacks any context about prerequisites or typical usage.

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