clinical_trials_enums

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

Annotations already declare readOnlyHint=true, and the description reinforces a read operation. It adds detail on output: 'Returns every enum type (Status, Phase, StudyType, et cetera) with all valid values.' No contradictions. Sufficiently transparent for its simple behavior.

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?

Three sentences with front-loaded purpose. Every sentence adds value: purpose, output, usage. Efficient but could be slightly tighter (e.g., combine output and usage).

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 no output schema, the description adequately explains the output format (enum types with values). For a simple listing tool, it covers the key aspects. Could mention if response includes descriptions or counts, but not necessary.

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?

Input schema has one optional parameter 'enum_type' with a description. Schema description coverage is 100%, and the tool description essentially repeats the schema's parameter info without adding new meaning. Baseline score of 3 is appropriate.

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 lists all valid enum values for ClinicalTrials.gov fields, with a specific verb 'List' and resource 'enum values'. It distinguishes from sibling tools that search or detail trials, though not explicitly contrasting.

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 explicit usage guidance: 'Use as a reference when building search filters or understanding field values.' This tells the agent when to apply the tool, though it could mention when not to use (e.g., for actual data queries).

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