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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds real behavioral value beyond that: the ranking heuristics, duplicate collapsing, ineligibility filtering, and the shape of the response ('why each one ranks and what to watch out for'). It omits data freshness, latency or result stability, keeping it from a 5.

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 opening sentence front-loads the core action, and the dense middle clause lists ranking factors that each carry information. The long run-on factor list is heavy but nearly every clause earns its place by mapping to a real input or behaviour.

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, the description usefully describes the return content ('why each one ranks and what to watch out for'), and it explains the filtering and ranking behaviour for an 11-param tool. Remaining gaps are a few undocumented params and no note on determinism or data recency.

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 only 45% across 11 params, so the description must carry weight, and it does explain the semantics behind cash_only, country/region-locking, can_travel/in-person, is_student, deadline runway, and include_generic. However it leaves limit, skills, interests and kind unaddressed, so it only partially compensates for the coverage gap.

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 (ranks), a specific resource (open HackList opportunities), and a scope (for a specific builder), plus the side effect of explaining each pick. This clearly separates it from the sibling search_opportunities/closing_soon, which merely list rather than rank and explain.

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 gives strong implicit routing: it is the curation/ranking tool that favours specific briefs and drops ineligible events, contrasting with plain listing siblings. It stops short of naming an alternative tool or stating an explicit 'use this when/not when', so it lands at a clear-context 4 rather than a 5.

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