Search YC startup jobs

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

With no annotations, the description carries the full burden, yet it only says 'API-only' and fails to mention the default fetchCompanies behavior, the required WAAS_COOKIE, or that a POST is made. It doesn't describe result shape or pagination.

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 sentences, front-loaded with verb and resource; no filler. However, the phrase 'API-only' is vague and the inaccurate filter list makes the brevity less useful.

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 5 parameters, no output schema, no annotations, and siblings, the description leaves out auth requirements, side effects (fetchCompanies), result format, and pagination defaults. It is not complete enough for an agent to call safely.

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%, so the baseline is 3; but the description actively contradicts the schema by advertising filters (jobType, remote, batch, industry) that are not in properties and are blocked by additionalProperties=false. This makes parameter selection riskier than if the description had stayed silent.

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 clear verb+resource (Search ... jobs) and gives an example query ('backend intern'), making it distinguishable from sibling startup search tools. However, it lists filters that aren't present in the schema, which slightly muddies the scope.

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?

Provides an explicit trigger example ('Use for backend intern') but no guidance on when to prefer this over yc_get_job or yc_search_startups, and doesn't mention that mirror filters are unsupported or that search results are only company_ids unless fetchCompanies is used. The usage context is clear but lacks exclusions.

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