get_dropoff_destinations

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

With no annotations, the description carries full burden. It discloses the meaning of the '(exited)' row, which is a key behavioral trait. It does not mention any destructive actions, which is appropriate for a data retrieval tool. The description is transparent about the output semantics.

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: two sentences that front-load the core action and provide immediate context. Every sentence adds value with no redundancy or filler.

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?

While the tool has 10 parameters and no output schema, the description sufficiently explains the main output ('where visitors go next') and the special '(exited)' row. The schema covers the parameters. The description could benefit from slightly more detail on the output structure (e.g., list of destination pages), but it is adequate for an agent to understand its role.

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 has 100% coverage with descriptions for all 10 parameters. The tool description adds minimal value beyond the schema, primarily by providing an example URL ('/pricing') and clarifying the substring match for 'from_url'. Given high schema coverage, a baseline of 3 is appropriate.

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 the tool's purpose: 'Given a URL, show where visitors go next or if they leave the site.' It uses a specific verb ('show') and resource ('where visitors go next'), and the parenthetical explanation of the '(exited)' row adds clarity. This distinguishes it from siblings like get_entry_exit_pages or get_session_paths.

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 a specific use case: 'Useful for understanding why people leave key pages like /pricing.' This implies when to use the tool, but does not explicitly state when not to use it or list alternatives. It gives clear context for its application.

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