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 is a paid action ($0.05 USDC), includes 3 searches, and returns up to 10 Markdown pages. However, it does not explain side effects (e.g., payment failure, result truncation beyond limits) or processing behavior, leaving significant ambiguity.

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 a single sentence, which is concise, but it reads more like a sales pitch than a function spec. Information about pricing and page count is front-loaded, but key operational details are missing. The structure is flat and not logically organized.

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 3-parameter tool with no output schema, this description is incomplete. It lacks explanation of return values (beyond Markdown pages), how query, limit, and max_pages interact, and operational prerequisites like wallet balance. It provides some context (cost, limits) but leaves major gaps for an agent to call correctly.

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, but it fails to explain any parameter. It mentions '3 searches' which could map to limit or max_pages, but not clearly. The default max_pages (8) contradicts the advertised 'up to 10 pages', adding confusion. No parameter is elaborated.

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 identifies the tool as a 'research package deep' with 3 searches and up to 10 pages in Markdown for one payment. It implies it performs research on a query but lacks an explicit verb+resource structure like 'Performs deep research and returns...'. It distinguishes itself from siblings via 'deep' and pricing, but doesn't clearly state its core function.

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?

No guidance is provided on when to use this tool versus alternatives such as ru_research, ru_search, or ru_page. There is no mention of scenarios for deep research vs. basic research, or any exclusion criteria. The user is left to infer its use.

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