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

Annotations already declare readOnlyHint=true, and the description adds meaningful context beyond that: the rationale for omitting repo/demo URLs, the presence of `submitted` and `submitted_at` fields for organizers, and the return envelope with `submitted_count` and `total`. This is valuable behavioral information not available from the schema or annotations.

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 longer than a bare minimum, but every sentence contributes distinct information: output contents, use case, submission filter, URL exclusion rationale, args, returns, and required scope. The structure is logical and front-loads the main purpose, though it could trim the rationale slightly without losing value.

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 only 3 optional parameters and no output schema, the description covers the needed ground: return shape, required scope, exclusions, and multiple use cases. There is no obvious missing information an agent needs to decide whether to call the tool or interpret its results.

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 covers 67% of parameters with descriptions (`submitted_only` and `recruiting_only`), while `eid` has no description. The description reinforces `submitted_only` by linking it to the organizer's chase-list use case but adds no new meaning for `eid` or `recruiting_only`. Baseline 3 is appropriate given high schema coverage and the description's minimal added parameter detail.

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 ('List') and resource ('hackathon teams') and enumerates the exact fields returned (name, size, startup, recruiting status). It clearly distinguishes this read-only listing from sibling mutation tools like ic_hack_team_create and ic_hack_team_join.

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?

It explicitly tells an agent when to use the tool ('Use this to find a team to join') and for an organizer's chase-list need. It also signals when not to use it ('repo and demo urls are NOT here'), though it does not name a specific alternative tool.

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