tiendanube_get_webhook

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

Being a GET operation, it's inherently read-only. Description lists returned info (endpoint, event type, auth, delivery status, error logs), which adds transparency beyond the absence of annotations.

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?

Two concise sentences with front-loaded purpose. Second sentence is slightly verbose but packs useful details.

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?

No output schema, but description lists key returned fields. Covers the essential context for a retrieval tool, though lacks error handling or pagination notes.

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 has 100% description coverage, so baseline is 3. Description does not add extra meaning beyond what schema already says about webhook_id and fields.

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?

Description clearly specifies retrieving a single webhook by ID, and distinguishes from listing webhooks by mentioning 'specific webhook' and 'unique ID'.

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 guidance on when to use (for comprehensive info, troubleshooting), but does not explicitly mention when not to use or point to siblings like list_webhooks.

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