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

With no annotations, the description carries the full transparency burden. It discloses the default field set (SEARCH_TOOL_DEFAULTS) and input format, but it does not mention edge cases (e.g., invalid IDs, missing fields), output structure, or rate limits. It adds some context beyond the schema but lacks comprehensive behavioral disclosure.

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 reasonably sized but contains redundancy: the first sentence 'Retrieve specific clinical trials by NCT ID(s)' is immediately restated in the next sentence 'This tool allows you to retrieve...'. The structure is clear with labeled parameters, but the redundancy adds unnecessary words.

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 covers the essential input parameters and default fields, but it does not explain the return format (no output schema) or error behavior. Given the tool's simplicity and availability of sibling tools like get_trial_details, more context would help but is not wholly missing.

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 schema provides descriptions for both parameters, but the tool description adds meaningful detail: the example for nct_ids and the explanation of the default behavior when fields is omitted. This goes beyond the schema's minimal 'NCT IDs to retrieve' and 'Specific fields to return'.

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 it retrieves clinical trials by NCT ID(s) with a specific verb ('Retrieve') and resource, distinguishing it from sibling search tools like search_trials_by_condition. However, it does not explicitly differentiate from the similarly named search_trials_nct_ids_only, so it falls short of a 5.

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 use when you have known NCT IDs, but it does not explicitly state when to use this tool versus alternatives like get_trial_details or search_trials_nct_ids_only. There is no when-not-to-use guidance, making it only minimally adequate.

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