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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine traits beyond them — a daily refresh cadence and curated tech-founder filtering — but says nothing about pagination behavior despite a limit parameter and default.

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 tight sentences with the resource scope front-loaded and the city-omission behavior second; nothing is padded. The second sentence duplicates the schema's `city` description, a minor redundancy.

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?

A read-only listing tool with rich annotations and an output schema needs only scope and behavior stated, which the description largely delivers. The remaining omissions — limit/pagination semantics and any routing hint versus the sibling venture tools — are modest given the structured fields already present.

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 33%: only `city` is documented in the schema, and the description merely repeats it ('Omit `city` to list the supported cities'). The `when` and `limit` parameters go unexplained beyond self-evident enum values and a default, so the description neither compensates for the gap nor adds meaning.

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 names the resource precisely ('curated startup and founder events in European tech cities') along with its scope and curation intent. It does not explicitly contrast with the siblings read_founder_ventures_page and search_founder_ventures, though the events-vs-ventures noun distinction makes them separable.

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?

Usage is only implied: 'filtered for tech-founder relevance and refreshed daily' signals the intended audience, and 'Omit `city` to list the supported cities' gives one operational instruction. There is no explicit when-to-use-this-vs-siblings guidance or condition for choosing among the three event/venture tools.

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