Close Session

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

While annotations already flag this as destructive, the description adds meaningful context: it closes *all active* scrape clients and cleans up resources. This goes beyond the simple destructive hint by specifying the scope and nature of the cleanup, though it does not detail side effects like termination of ongoing operations.

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 concise sentence that clearly conveys the action. Every word earns its place, 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?

For a zero-parameter tool with an output schema and a destructive annotation, the description is sufficient. It clearly states what the tool does. It could mention whether calling it without an active session is safe, but this is a minor gap given the tool's simplicity.

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 tool has zero parameters, so the description need not add parameter semantics. The input schema is empty and fully covered. A baseline of 4 is appropriate since there is no parameter information to provide.

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 action: 'Close all active scrape clients and clean up resources.' It uses a specific verb ('close') and resource ('scrape clients'), distinguishing it from sibling tools that are getter functions for threads profiles and user threads.

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 as a cleanup or teardown operation, but it does not explicitly state when to use it (e.g., 'call when done scraping') or contrast it with alternatives. Sibling tools are clearly different in purpose, but no direct guidance on when to invoke this tool is provided.

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