Search the Tamperbox API specification

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

With annotations already declaring readOnly, idempotent, closed-world behavior, the description adds meaningful operational context: no API requests are made, code is limited to 64 KiB, default timeout is 15 seconds, and returned JSON is capped at 2 MiB. These details go beyond the annotations and are consistent with them.

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 contains valuable constraints but is dense and front-loads a long topic list before the actual execution semantics. Some sentences could be tightened, and the key limits are buried at the end.

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?

An output schema exists, so return-shape explanation is not required. Still, for a code-execution tool with two parameters and 0% schema coverage, the description omits explicit timeout parameter semantics and does not clarify the relationship to the sibling 'execute' 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?

Schema description coverage is 0%, so the description must compensate. It clarifies that 'code' is an async JavaScript function body and gives size/time/return limits, but it never explicitly explains the 'timeoutMs' parameter name, units, or maximum, leaving part of the schema undocumented.

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 eventually states a specific action—running an async JavaScript function body over the local OpenAPI spec—and lists discoverable domains. However, the tool is named 'search' while its core behavior is code execution, and the sibling 'execute' is never referenced, leaving the purpose somewhat mixed.

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?

It implies usage through instructions like inspecting 'spec["x-tamperbox-directory"]' for website categories and filtering operations by tags. But it gives no explicit when-to-use guidance versus the 'execute' sibling and no exclusions or alternatives.

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