get_agent_webhooks

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

No annotations are provided, so the description must fully disclose behavioral traits. It indicates a read operation ('list') but does not mention authentication needs, rate limits, or what happens if the agent has no subscriptions. The description lacks depth beyond the basic action.

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 clear sentence that directly states the purpose and provides specific event types. It is concise and front-loaded with no unnecessary words.

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 no output schema, the description does not explain return values or structure. For a list tool, it would be helpful to mention that the response contains an array of subscriptions with webhook IDs and events. The description is adequate but incomplete.

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?

With 100% schema description coverage, baseline is 3. The description adds value by specifying the events (pre-conversation, etc.) and clarifying that it lists 'current' subscriptions, which goes beyond the schema's simple parameter description.

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 'List an agent's current webhook subscriptions' specifying the verb 'list' and resource 'webhook subscriptions'. It also mentions the events (pre-conversation, post-conversation, analytics-completed), distinguishing it from sibling tools like 'get_webhooks' and 'get_webhook_events'.

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?

The description implies usage for retrieving subscriptions for a specific agent but does not provide explicit guidance on when to use versus alternatives like 'get_webhooks' or when not to use. No exclusions or alternative references are given.

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