search_footprint

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

No annotations, but description discloses passive, public-source collection, return types (structured results and graph nodes/edges), and data source behavior. Does not detail rate limits or error handling, but covers key behavioral traits.

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?

Three sentences, front-loaded with main purpose. Includes necessary legal note. Could be slightly more concise, but generally well-structured.

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 complexity and lack of output schema, description adequately explains return types, data sources, and usage constraints. Does not cover error cases or target finding failure, but sufficient for typical use.

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 coverage is 67%; description adds value by explaining 'entity-type-aware' for target and that max_queries are billable. However, it does not specify target format or provide additional details beyond schema descriptions for json_output and max_queries.

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?

Clearly states the tool finds real public profiles by searching the web, with entity-type-awareness for various inputs. Distinguishes from siblings like search_email or search_username by being a broader, multi-type search.

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?

Describes data sources (DuckDuckGo, optional Bright Data) and includes a usage restriction ('Authorized use only'). Lacks explicit contrast with sibling tools but the context of 'entity-type-aware' implies a comprehensive search.

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