Search HackList (connector)

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the bar is lower. The description adds genuinely useful non-schema context: it returns ids intended to be passed to fetch, which is the key behavioral contract given there is no output schema.

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 short sentences, front-loaded with what is searched and what is returned, with the compatibility note relegated to a parenthetical. Nothing is redundant or padded.

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 one-parameter, non-destructive read tool with no output schema, the description covers the essential contract: what is searched and that ids are returned for fetch. The only gap is the absence of explicit routing versus the sibling search_opportunities, which would make the definition fully self-sufficient.

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 a single parameter with 100% schema description coverage ('Search keywords'), so the schema already carries the semantics. The description adds no syntax, matching, or format detail beyond what the schema provides; baseline 3 is appropriate.

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 states a specific verb (search) and resource (open HackList hackathons, grants and programs) with the search dimension (by keyword) made explicit. It also hints at differentiation from the sibling search_opportunities by labeling itself a compatibility tool, though it never directly names or contrasts with that sibling, so the distinction is implied rather than 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?

The parenthetical 'Compatibility tool for ChatGPT connectors and deep research' implies a usage context, but it never says when to prefer this over the near-identical sibling search_opportunities, nor does it state exclusions. An agent can infer the niche, but the routing guidance is left to guesswork.

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