get_web_searches

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

No annotations provided, so description must cover behavioral traits. It describes a read-only retrieval of all searches, which is non-destructive, but does not disclose return format, pagination, or authentication needs. Adequate for a simple list tool but lacks detail.

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 that convey purpose and usage without redundancy. Every token 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 no parameters and no output schema, the description covers the essential purpose and usage. However, it could hint at the return type or ordering. Still, it is mostly complete for a simple list 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?

Tool has zero parameters and schema coverage is 100% (empty schema). Description adds no parameter-specific info, but baseline for 0 parameters is 4 as no further detail is needed.

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 clearly states the tool's function: retrieve all web searches across all agents, using a specific verb and resource. It distinguishes itself from sibling tools (e.g., log_web_search, specific query tools) by focusing on aggregated search history.

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?

Explicitly advises using the tool to avoid duplicating research, implying a when-to-use scenario. Does not explicitly state when not to use or name alternatives, but the context and sibling tool names (e.g., log_web_search) provide sufficient inference.

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