extract_yc

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

Annotations already indicate read-only and open-world behavior. The description adds a useful transparency note about freshness ('Freshness is unknown'), which helps set expectations. However, it does not mention rate limits or data volume, though these are not critical given the read-only annotation.

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 two sentences, direct, and information-dense. It covers the action, the URL pattern, the expected output, and the freshness caveat without any redundancy or irrelevant detail.

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?

Since there is no output schema, the description compensates by listing the returned fields (name, batch, tags, description) and noting the freshness limitation. It does not cover error handling or pagination, but for a simple scraping tool, the provided context is sufficient for most use cases.

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 url parameter is well documented with an example, but max_length has no description in the schema or the description text. The name is somewhat self-explanatory, and the default value (6000) hints at output length, but the lack of explicit documentation keeps this at a mid-level score.

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 action ('Scrape YC company listings') and a clear resource (Y Combinator companies). The URL template further clarifies the target, and the tool is clearly distinguished from sibling extract_* tools by its YC focus.

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 a concrete usage instruction ('Use https://www.ycombinator.com/companies?query=KEYWORD to find startups in a space') and describes what it returns. It does not explicitly contrast with alternatives, but the specific YC scope and keyword-based query make usage clear.

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