uc_session

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

Annotations already declare read-only, idempotent, non-destructive, and open-world behavior. The description adds valuable operational context beyond that: the cf_clearance cookie is short-lived, refreshing cookies.json and reloading fixes Cloudflare errors, and no restart is needed. It does not explain what clear_cache changes or what request budget means.

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?

Two short paragraphs, front-loaded with the tool's purpose and followed by focused operational guidance. Every sentence earns its place and there is no 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?

An output schema exists, so return values need not be explained, and rich annotations cover safety and idempotency. However, the description omits any explanation of clear_cache and only names session-health/request-budget concepts without elaborating, leaving a meaningful gap for a two-parameter tool.

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 carry both parameters. It explains reload=True well by giving the condition and purpose, but it never mentions clear_cache, leaving one of two parameters undocumented beyond its name.

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 first line names the resource (session) and the state it reports (health, request budget, cache), so an agent can identify it as a session diagnostics tool. It is not verb-led, but it is specific enough and clearly distinct from the uc_search/thread/forum/fetch siblings.

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 second paragraph gives a concrete when-to-use scenario for reload=True: after re-exporting cookies.json, when Cloudflare errors occur, and notes no restart is needed. It does not discuss when to call the tool itself, when to use clear_cache, or alternatives, but the operational context is clear.

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