browse_answer

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. While it outlines the pipeline steps, it fails to mention critical behavioral traits such as execution time, rate limits, authentication needs, error handling, or what happens if steps fail. For a complex multi-step tool with no annotations, this is a significant gap in transparency.

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 appropriately sized and front-loaded, listing key steps in a single sentence without unnecessary words. However, it could be more structured by separating steps with commas or bullet points for clarity, and some phrases like 'Full deep research pipeline' are slightly redundant with the tool name 'browse_answer'.

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?

Given the tool's complexity (multi-step pipeline), lack of annotations, no output schema, and minimal parameter guidance, the description is incomplete. It doesn't explain return values (e.g., format of the 'structured answer'), error conditions, or performance considerations, leaving the agent with insufficient context for reliable use.

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 schema has 1 parameter with 0% description coverage, so the description must compensate. It implies the 'query' parameter drives the research pipeline but doesn't add meaning beyond that (e.g., format expectations, length limits, or examples). Since there's only one parameter, the baseline is 4, but the description provides minimal semantic value, resulting in a score of 3.

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 with specific verbs ('search the web, fetch pages, extract claims, build evidence graph, generate a structured answer') and resources ('with citations and confidence score'), distinguishing it from sibling tools like browse_search or browse_extract by describing a comprehensive multi-step pipeline rather than individual operations.

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 no guidance on when to use this tool versus alternatives like browse_search (for simple searches) or browse_compare (for comparisons). It implies usage for 'full deep research' but lacks explicit when/when-not instructions or prerequisites, leaving the agent to infer context from the tool name and description alone.

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