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

Annotations already establish readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds little beyond that: it never explains how companies are scored, what 'fit to what you sell' requires as configuration, or what happens with unscored/unmatched rows — all of which matter for a scoring tool.

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 literally begins twice with the same clause and both copies cut off with an ellipsis, so the content is duplicated and unfinished rather than front-loaded and complete. Nearly half the text is wasted repetition.

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?

With no output schema, an opaque single nested 'input' object, and a truncated description, an agent cannot know what the response looks like, how signals are ranked, or what to pass in. The description does not fill the gap that the schema and annotations leave.

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?

There is one parameter named 'input' with 100% schema description coverage, but that coverage is just a pointer to the external Apify page. Per the high-coverage baseline a 3 applies, though the description itself offers no hint about what the nested object should contain.

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 conveys the general idea — ingest a Crunchbase/funding scraper dataset and get recently funded companies scored as buying signals — but the verb+resource is phrased loosely as 'point it at', and the sentence trails off mid-clause, so the end-to-end function is never fully stated.

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?

There is no guidance on when to choose this over the many nearby siblings (us_funding_rounds, signal_radar, qualified_leads, b2b_lead_list_builder, ai_prospecting_pipeline). The only contextual cue is 'point it at any Crunchbase/funding scraper's dataset', which describes input type, not selection criteria or prerequisites.

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