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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions return fields and search criteria but does not disclose whether the operation is read-only, any authentication requirements, error handling, or behavior for empty results. For a search tool, the description adds limited behavioral context beyond the obvious read-only nature implied by 'search'.

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 concise and front-loaded, stating the primary action and resource in the first sentence, followed by a clear list of returned fields. Every sentence adds value with no redundant or extraneous content.

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?

The description adequately covers the tool's purpose and return fields, which is important given no output schema. It does not mention sorting, pagination, or how the limit parameter affects results, but those details are captured in the schema. For a search tool with six optional parameters, the description is reasonably complete, though it could mention when to use sibling tools.

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 description coverage is 100%, so the parameters are already well-documented in the schema. The description lists the search dimensions (condition, intervention, sponsor, status, phase) which map to parameters, but it does not add new semantic meaning beyond the schema. Examples like 'Pfizer' and 'metformin' provide minor illustrative value but do not significantly enhance understanding.

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 ('Search') and identifies the exact resource ('clinical trials on ClinicalTrials.gov') and the search criteria (condition, intervention, sponsor, status, phase). It clearly distinguishes from sibling tools like get_trial_details and get_trial_stats, which focus on specific trial info and statistics rather than discovery.

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 implies the tool is for searching trials by various criteria, providing enough context for when to use it. However, it does not explicitly mention alternatives or conditions when this tool should not be used, such as pointing to get_trial_details for detailed trial information. No exclusions or alternative recommendations are given.

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