topai_b2b_data_leads

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false. The description restates 'Stateless, read-only, idempotent query', which largely duplicates the annotations rather than adding new context. It does not add anything about result ordering, data freshness, or rate limits beyond the structured hints.

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 the core purpose, followed by usage guidance and the invocation contract. No filler, every clause earns its place.

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 3-param read-only query tool with no output schema and full param documentation, the description is essentially complete: purpose, scope, alternative, and behavior are all present. The only minor gap is that it does not clarify output shape or sorting, which matters slightly without an output schema.

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%, with each parameter including bounds and examples, so the baseline is 3. The description only summarizes that filtering is by industry, country, and limit, adding no syntax, format, or edge-case detail beyond the schema.

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?

States a specific verb and resource ('Queries verified B2B company and executive lead records') and names the filter dimensions (industry vertical, ISO country code, result limit). It also explicitly distinguishes itself from the sibling enrichment tool.

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?

Gives positive usage contexts (prospect lists, sales pipelines, market landscapes) and an explicit exclusion: when you have a specific domain needing technographic profiling, use topai_company_enrichment. Both when-to-use and when-not-to-use are covered with the named alternative.

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