search

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

Discloses the default time filtering behavior (none) but omits other behavioral traits such as rate limits, result count limits, error handling, or expected latency. With no annotations, the description should provide more behavioral context.

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 fluff. First sentence provides purpose and key attributes (citations), second sentence clarifies default behavior. Every phrase earns its place.

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?

Adequate for a simple search tool with two parameters and no output schema. Mentions citations and default filtering, but lacks details on result structure, pagination, or potential errors. Could be more comprehensive.

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%, so baseline is 3. Description adds no new information beyond the schema; it restates the default for the recency filter but does not enhance understanding of parameters.

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?

Clearly states the tool performs a web search using Traylinx's API, indicating the verb (search) and resource (web). Adds specificity by noting results include citations. With no sibling tools, differentiation is not required.

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?

Implies usage for web search but does not explicitly guide when to use it over alternatives. Mentions default no time filtering, which helps with recency filter decisions, but lacks explicit context or exclusion scenarios.

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