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

No annotations are provided, so the description carries full responsibility. It discloses the data source (NIH ClinicalTrials.gov), data type (interventional, industry-sponsored), ordering, pagination (cursor-based, up to 1000/page), and that it is an observational registry (not a prediction). It also mentions pricing. It does not mention authentication or rate limits, but these are not critical for a read-only feed.

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 a single, well-structured sentence that efficiently front-loads the purpose and then details pagination, filters, and output. It is concise yet comprehensive, with no unnecessary words. Minor improvement could be splitting into two sentences for readability.

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 9 parameters with full schema coverage and no output schema, the description provides all necessary context: data source, scope, filtering options, pagination details, and the fields included in rows. It is sufficient for an agent to understand the tool's capabilities and invoke it correctly.

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%, meaning all 9 parameters have descriptions. The description adds value by explaining the broader context: the feed is over interventional industry-sponsored studies, provides specific fields (sponsor, phase, status, conditions, enrollment, dates, site count, US states), and is cursor-paginated. This contributes meaning beyond the schema's per-parameter descriptions.

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 clearly states the tool's function: identifying companies that just opened a new clinical trial or site, using a bulk feed from NIH ClinicalTrials.gov. It specifies the resource (clinical trial feed), scope (interventional, industry-sponsored), and ordering (newest-first by registry-posting date). This distinguishes it from sibling tools like trials_trials_search and trials_sites_search, which are search-oriented.

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 provides clear context: it's a cursor-paginated feed suitable for monitoring new trial starts. It lists filterable criteria (sponsor, phase, status, condition, intervention type, site state, since). However, it does not explicitly mention when to use this tool versus alternatives like trials_trials_search, nor does it state when not to use it. This is a minor gap.

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