webhook_list

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

Discloses read-only nature, absence of URLs/secrets in output, environment variable requirement (OMNIFOCUS_WEBHOOKS_ENABLED=1), and return order. Fully transparent about all behavioral traits beyond what schema or annotations (none) provide.

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?

Description is well-structured with front-loaded purpose, but contains several sentences that could potentially be condensed. Still efficient and earns its length with 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?

Given zero parameters and no output schema, the description fully covers return format, order, safety characteristics, and configuration requirement. No gaps remain.

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?

No parameters exist in schema (0 params), so baseline is 4. Description adds no parameter info, but none is needed. No improvement possible.

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 it lists webhooks by name, trigger, and createdAt. It distinguishes from sibling tools like webhook_delete and webhook_register, making the purpose unambiguous.

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?

Explicitly advises when to use (confirm wired-up webhooks) and when not to (retrieve URLs/secrets). References alternative tool webhook_delete. Provides clear context for appropriate usage.

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