create_webhook

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

No annotations provided. Description mentions return value (GID) and need to verify delivery. Does not disclose potential side effects, rate limits, or authentication requirements. Partial coverage.

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?

Five concise sentences, each serving a purpose. No redundant information. Front-loaded with main action and common topics.

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?

Covers all essential aspects: topic suggestions, callback requirement, field filtering, metafield opt-in, return value, and verification advice. Lacks mention of overwriting behavior but still sufficiently complete for a creation tool.

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 80%, description adds value by listing common topics and explaining the benefit of includeFields. However, it mostly echoes schema descriptions. Adequate but not exceptional.

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?

Clear verb ('Subscribe') and resource ('webhook topic') with specific endpoint mention. Lists common topics to clarify scope. Distinct from sibling tools like update_webhook or 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?

Provides some context: callbackUrl must be HTTPS in production, and verification is needed. However, no explicit guidance on when to use this vs. sibling tools like update_webhook or list_webhooks.

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