Search Apify docs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is clear. The description adds that results include URL and limited content, and that full content should be fetched via fetch-apify-docs. No contradictions. Minor omission: no mention of rate limits or pagination behavior beyond offset/limit.

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 moderately lengthy but well-structured with clear sections, bullet points, and bolded terms. It is front-loaded with the core purpose. Could be slightly more concise, but every sentence adds value.

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?

Given the tool's complexity (multiple documentation sources, pagination, integration with a sibling tool), the description is thorough. It covers when to use, how to parameterize, and what to expect in results. The output schema exists, but the description still provides useful context on return format.

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 100%, so baseline is 3. The description adds meaningful context beyond the schema, such as query formatting ('Use only keywords, do not use full sentences'), and elaborates on docSource options with detailed explanations. This justifies a score above baseline.

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 'Search Apify and Crawlee documentation using full-text search' and explicitly distinguishes from search-actors by saying 'Do not also call search-actors unless the user asks to find Actors in the Apify store.' It uses specific verbs and resources.

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 provides explicit context on when to use this tool vs alternatives (e.g., 'Do not also call search-actors...'), and details which docSource to select with examples. It also advises to prefer platform documentation over Academy content.

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