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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the auth requirement ('Needs a free StartupHub.ai account') and an equivalent REST endpoint. It omits rate limits and cost, but adds real value on top of 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?

Front-loaded with the core action and efficient throughout, with each sentence carrying distinct information (scope, accepted inputs, dossier contents, breadth, endpoint, auth). Slightly verbose in enumerating dossier components, but no filler.

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?

There is no output schema, and the description compensates by enumerating the dossier contents (company facts, funding, people, technographics, social/web presence, AI signals). Combined with annotations and the auth note, an agent has enough to invoke it correctly.

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 100% and the single parameter is fully self-documented; the description's list of accepted input types simply restates the schema. Baseline 3 is appropriate since it adds no syntax or format 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+resource ('run a deep-intelligence lookup on any entity') and explicitly positions it as 'the widest single call in the catalogue,' which cleanly distinguishes it from focused siblings like enrich_company, get_startup, or search_people.

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?

It gives clear input context (name, company, domain, LinkedIn URL, or email) and hints at breadth via 'widest single call,' but never explicitly says when to prefer this over the many narrower siblings such as enrich_company or get_company_funding. Usage is implied rather than routed.

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