list_browsing_tasks

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

Beyond the readOnlyHint annotation, the description reveals that list status is approximate and that 'running' also covers queued and not-yet-reconciled tasks, adding valuable behavioral context without contradiction.

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 concise sentences with a clear purpose statement and key usage notes, no wasted words.

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?

The description covers core functionality, pagination, status nuance, and references the detailed get tool. It could mention that results are scoped to the authenticated user, but the presence of an output schema reduces the need for return value details.

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?

With 0% schema description coverage, the description mentions 'cursor pagination' and 'status filtering' but does not explain the individual parameters (limit, cursor, status) or how to use them effectively, leaving significant gaps.

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 lists one-time browsing tasks for the authenticated user, distinguishing it from sibling list tools (list_research_tasks, list_scouts) by specifying 'browsing tasks' and 'one-time'.

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?

Describes pagination and status filtering, and directs users to get_browsing_task_result for authoritative status, providing good contextual guidance. However, it could more explicitly state when not to use this tool (e.g., for single task details) and list alternatives.

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