Penny Search

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose useful traits: the search is live, low-cost, ranked, and pay-per-call via x402 at $0.004. However, it does not describe the return structure, freshness value semantics, or rate/error behavior, so transparency is partial.

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 compact and front-loaded, with purpose, routing guidance, and pricing in three sentences. The use-case list is slightly redundant—'recent news' and 'fresh facts' overlap with 'current information'—but there is no fluff or filler.

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?

For a simple search tool, the description gives enough context to invoke it: what it searches, when to prefer it, and what it costs. But it omits parameter behavior (`freshness`, `limit`) and the exact result shape, and there is no output schema or sibling context to fill those gaps.

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%, and the description does not explain the three parameters directly. 'Query' and 'limit' are fairly self-evident from their names, and 'fresh facts' hints at the `freshness` parameter, but accepted values and how `limit` or `freshness` affect results are left unspecified.

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 names a specific verb and resource: 'live web search' for 'current information, recent news, fresh facts, documentation lookup, research, source discovery, and web grounding.' It also clarifies the output character by saying 'ranked current web results,' making the tool's purpose unambiguous even without sibling tools.

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 to 'Use this first when ranked current web results are enough' and to escalate to a deeper scraping or specialist tool only when capabilities are missing. This gives clear when-to-use and when-not-to-use guidance, and the cost disclosure helps an agent decide based on budget.

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