Web Presence (Google Search)

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

Annotations already indicate this is a read-only, non-destructive, idempotent, and open-world operation. The description adds value by specifying that it searches Google and detects competitor overlap, which provides context beyond the annotations. However, it does not detail behavioral traits like rate limits, authentication needs, or result format, which would be helpful given the lack of an output schema.

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 concise and front-loaded, consisting of two sentences that efficiently convey the tool's purpose and key functionality. Every sentence adds value without redundancy, making it easy to understand quickly.

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 (a search operation with one parameter), rich annotations, and 100% schema coverage, the description is mostly complete. It explains the purpose and context well. However, the lack of an output schema means the description could benefit from mentioning what the search returns (e.g., links, summaries), slightly reducing completeness.

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?

The input schema has 100% description coverage, with the 'brand_name' parameter well-documented in the schema itself. The description adds minimal semantic context by implying the brand name is used for Google searches, but it does not provide additional details beyond what the schema already covers, such as formatting or usage examples.

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 specific action ('Search Google'), the resource ('existing companies or products'), and the input ('using a brand name'). It distinguishes this tool from siblings by specifying its focus on Google search results and competitor overlap detection, unlike tools like 'brandomica_check_trademarks' or 'brandomica_check_domains'.

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 clear context for when to use this tool: to find existing companies or products via Google search, particularly for detecting competitor overlap not in formal registries. However, it does not explicitly state when not to use it or name specific alternatives among the siblings, such as 'brandomica_check_trademarks' for registry-based checks.

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