webhooks.list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'List' implies a read operation, the description fails to confirm safety (read-only, non-destructive), mention pagination behavior, or indicate the scope of returned data (e.g., all webhooks vs. filtered).

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 extremely concise at only 4 words. While appropriately brief for a zero-parameter tool, it marginally exceeds the threshold of underspecification given the lack of output schema and annotations—every word earns its place, but additional context is needed.

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 the absence of an output schema and annotations, the description provides the minimum viable information. It adequately identifies the operation but fails to clarify the return structure (array of webhook objects) or distinguish it from sibling retrieval operations, leaving gaps an agent would need to infer.

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?

The input schema contains zero parameters, which per scoring guidelines establishes a baseline of 4. The description correctly implies no filtering is available by omitting any parameter references.

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 uses the specific verb 'List' and identifies the resource as 'Ryft webhook endpoints', making the basic purpose clear. However, it misses the opportunity to distinguish this from the sibling 'webhooks.get' tool (singular retrieval vs. collection listing).

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?

No guidance provided on when to use this tool versus 'webhooks.get' or other webhook operations. It does not mention prerequisites (e.g., needing active webhooks) or if this retrieves all webhooks across the account or only active ones.

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