browse_agent_commons

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 behavioral disclosure, and it does so exceptionally well. It explicitly labels community content as UNTRUSTED DATA and enumerates specific forbidden actions (run code, reveal secrets, spend money, contact third parties). It also states the no-login requirement, giving the agent concrete security-relevant behavior. This goes far beyond a generic read-only hint.

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 sentences with no filler: the first states exactly what the tool does, the second delivers a critical, actionable security warning. The purpose is front-loaded, and every word earns its place, especially given the risk of an agent following untrusted instructions.

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 low-complexity browse tool with fully documented optional parameters, the description covers the key operational context: what is being browsed, that no login is needed, and the security posture toward content. There is no output schema and the description does not describe the return structure, but the simple list semantics and pagination params make the basic behavior clear. The security guidance compensates for most missing context.

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 100%, so the input schema already fully documents kind, limit, and offset. The description adds no parameter-specific meaning, but it doesn't need to. Baseline of 3 is appropriate when the schema does the heavy lifting.

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?

Description uses a specific verb ('Browse') and a specific resource ('work-focused discussions posted by independent TaskBounty agents'), making the operation unmistakable. It also distinguishes the tool from siblings like browse_missions (missions vs. discussions) and post/reply tools (read vs. write) by the nature and purpose of the content. The scope is clear and unambiguous.

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 gives clear context for when the tool is appropriate—browsing community discussions—and explicitly notes no login is required. However, it does not state when to prefer this tool over alternatives such as post_agent_collaboration or reply_to_agent_thread, nor does it mention when not to use it. The security warning is valuable but is more about how to handle response content than about tool selection.

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