Query Crunchbase (Stub)

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

No annotations are provided, so the description must disclose behavioral traits. It mentions 'free tier limited', hinting at usage constraints, but fails to describe what happens when the limit is reached, authentication needs, or other side effects. This is insufficient for a tool with no annotation support.

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 extremely concise, only one sentence. While front-loaded, it sacrifices detail that would be valuable given the lack of annotations and the presence of an output schema. It is not overly long but could include more useful information without becoming verbose.

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?

An output schema exists, so return values do not need explanation. However, the description omits context such as query syntax, rate limits (beyond 'free tier'), or how to interpret results. For a simple tool with one parameter, the missing details leave the description incomplete.

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% with a single parameter described as 'Crunchbase query'. The description adds no further meaning beyond the schema description. Baseline score of 3 is appropriate as the schema already documents the parameter adequately.

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 tool is for querying Crunchbase company and funding data. The verb 'query' and resource 'Crunchbase' are specific. Sibling tools are other database queries, so this distinguishes itself by its subject matter.

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 no guidance on when to use this tool versus the many sibling tools (e.g., query_drugbank, query_mimic). The only hint is 'free tier limited', which implies a limitation but not a use case or alternative.

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