rank_best_targets

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

With no annotations, the description must carry the behavioral disclosure burden. It does disclose that only 'verified, fresh upcoming/ongoing' hackathons are ranked and that include_demo is for local walkthrough fixtures only. It does not disclose how ranking is computed, whether it uses the project profile, or any side effects, but the tool appears to be a read-only ranking operation.

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?

Two short sentences, front-loaded with the primary purpose and followed by a precise usage note. Every word earns its place; there is no fluff or 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?

Given the presence of an output schema, the description does not need to explain return structure. It covers the tool's purpose, the filtering criteria ('verified', 'fresh', 'upcoming/ongoing'), and the special include_demo case. It could be more complete by stating how 'best' is determined or that project_id is required, but these are minor given the schema.

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?

The schema has 0% description coverage, and the description only explains include_demo behavior. It does not clarify the meaning of project_id or top_k beyond their names/defaults. Because the schema property names are reasonably self-explanatory, this is still somewhat usable, but the description leaves important semantic gaps.

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 uses a specific verb ('Rank') and a clear resource ('verified, fresh upcoming/ongoing hackathons for a project'), immediately distinguishing this from sibling tools like search_hackathons or get_hackathon_details. It states the core function and scope in one sentence.

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 clearly implies this tool is for obtaining a ranked list of currently relevant hackathons for a project. It also supplies a specific usage caveat ('Set include_demo=True only for the bundled local walkthrough fixtures'), which helps prevent misuse. However, it does not explicitly contrast with alternatives like score_project_fit or search_hackathons.

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