research_pack

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

Despite no annotations, the description discloses a critical behavioral trait: it returns payment requirements (x402) if unpaid, indicating a conditional execution. This is valuable transparency. However, it does not disclose other behaviors like whether it mutates data or requires specific permissions.

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, concise and front-loaded with the main action. However, it could be slightly clearer by splitting into separate clauses for the paid search behavior and the payment fallback.

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?

The description does not cover the return value or output schema, even though one exists. Parameter details are lacking. Given the tool's complexity (paid search, extraction, citations, payment handling), the description is incomplete for an agent to use effectively.

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?

With 0% schema description coverage, the description should explain each parameter. It mentions 'paid search' and 'page extraction' but does not define parameters like 'max_results', 'extract_pages', 'payment', or 'payment_identifier'. The agent must infer meanings.

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 clearly states the tool performs a paid search combined with page extraction and citations, and it indicates a fallback behavior when unpaid. This distinguishes it from siblings like 'search' (basic search) and 'extract_page' (standalone extraction).

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 implies it's for paid search with extraction needs, but it does not explicitly state when to use this tool versus alternatives like 'search' or 'extract_page'. No exclusions or prerequisites are mentioned.

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