notion_list_webhooks

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

No annotations are provided, so the description carries the full burden of disclosing behavioral traits. It mentions authentication routing but does not explain pagination, rate limits, error behavior, or output format. For a read operation, the description is insufficient. Score 2 for minimal behavioral disclosure.

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 three sentences, but the second sentence about routing is superfluous for agent decision-making. The first and third sentences are on-topic. It could be more concise by removing the routing detail. Score 3 for some unnecessary content, but overall not overly verbose.

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 single parameter and output schema presence, the description should clarify how to construct the arguments JSON. It does not provide enough guidance for effective invocation. The output schema compensates for return value explanation, but the input remains ambiguous. Score 2 for incomplete context regarding usage.

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 0%, so the description must compensate. It says 'arguments: JSON string of arguments for the connector operation,' which adds context that the parameter is a JSON wrapper but does not specify what keys or values are expected (e.g., filter, limit). This leaves the agent guessing about the required payload. Score 2 for adding only minimal meaning 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?

The description states it's a Notion connector operation 'list_webhooks', which clearly indicates the tool lists webhooks. The name and first sentence convey the purpose. However, it does not explicitly distinguish from similar list tools (e.g., notion_list_users), but the unique resource 'webhooks' differentiates it. Score 4 for clear verb+resource, missing explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives like notion_create_webhook or notion_delete_webhook. There is no context on prerequisites, use cases, or exclusions. The routing information is irrelevant for usage selection. Score 2 for lack of when-to-use or alternatives.

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