log_web_search

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

With no annotations, the description carries the burden. It discloses that the tool returns a warning if another agent already searched for something similar, which is the key behavioral aspect. It does not mention side effects, auth, or rate limits, but for a logging tool this is acceptable.

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 extraneous words. The description is front-loaded with the action and immediately provides usage context. Every sentence adds value.

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 simplicity of the tool (one required param, no nested objects), the description covers purpose, usage guidance, and return behavior. No output schema is needed as the return is a warning message, which is described. The description is complete.

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 coverage is 100%, and the schema already describes the param. The description does not add new information about the parameter beyond saying it's a web search to be performed. Baseline score is appropriate.

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 logs a web search. The verb 'Log' and resource 'web search' are specific. It distinguishes from sibling tools, which are about querying databases or retrieving data, by focusing on logging an action.

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 explicitly says 'Call BEFORE every web search to avoid duplicate research across agents.' This provides clear guidance on when to use the tool and hints at when not to (if a warning is returned, you may reconsider the search).

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