Find First Google Organic Result

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

Annotations declare readOnlyHint and openWorldHint. The description adds that it costs 2 credits per call and returns the first organic result, providing useful behavioral context beyond the annotations.

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?

Description is concise with a clear title, brief purpose statement, cost, and parameter description. No wasted words, but the structure could be more front-loaded for quick scanning.

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 tool with one parameter and no output schema, the description covers purpose, cost, and basic behavior. It lacks explicit error handling or result format details, but is largely complete.

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?

Only one parameter with 100% schema description coverage. The description adds 'Enter text made of the column you want to search' which provides slight additional context, but overall adds limited meaning beyond the schema's 'Select values you want to search'.

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 it returns the first organic Google result for a query, with examples of use cases like finding a person's website or LinkedIn. This distinguishes it from sibling tools such as derrick_serp_first_page.

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 usage by stating it is useful for finding a person's website or LinkedIn, but it does not explicitly compare with alternatives or provide when-not-to-use conditions. Lacks explicit guidance on choosing this over derrick_serp_first_page.

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