List Company Webhooks Resources

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description correctly confirms it returns data without mutation. It adds that the response is a paginated JSON array with metadata, which is useful behavioral detail. No contradiction; description adds value beyond 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?

Four sentences covering purpose, usage, pagination, and endpoint reference. All sentences are necessary and no fluff. Front-loaded with key information.

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 exists, so the description appropriately notes a paginated JSON array with metadata. It also provides the API endpoint and required parameters. Given the read-only annotation and simplicity of the tool, this is complete enough.

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 description coverage is 100%, so parameters are well-documented in the schema. The description additionally explains the purpose of page and per_page for pagination control and mentions required parameters, which adds useful context beyond the schema.

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 states it returns a list of webhooks resources for the company and specifies use cases: enumerating webhooks for a paginated overview, finding IDs, or filtering by query parameters. This is specific and differentiates from many sibling list tools.

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 direct guidance on when to use the tool: 'Use this to enumerate Webhooks when you need a paginated overview, to find IDs, or to filter by query parameters.' It also mentions pagination parameters and required fields, giving clear context. No explicit alternatives or 'when not to use' but sufficient for a read-only list tool.

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