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

With no annotations, the description carries the full burden of behavioral disclosure. It does not specify the output format (e.g., counts per phase), whether the tool is read-only, or any side effects. The only behavioral detail added is the max_studies default, which is already present in the schema, so the description contributes little beyond structured data.

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 first two sentences are redundant: 'Analyze the distribution...' and 'This tool analyzes the distribution...' say essentially the same thing. The rest is a structured input list that is concise but the repetition makes it less efficient than it could be.

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 explains inputs but omits any description of the return value or how the analysis is presented. Since there is no output schema, the description should at least mention that it returns phase distribution counts. It also does not clarify whether criteria are combined or how max_studies affects the analysis beyond being a cap. Given the tool's simplicity, these gaps leave it incomplete.

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 baseline is 3. The description repeats parameter names and brief explanations (e.g., 'A list of medical conditions to filter the analysis'), but these add no meaning beyond the schema's own descriptions. It does mention the default for max_studies, though the schema already includes 'default: 1000'.

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 specific verb and resource: 'Analyze the distribution of trial phases'. It explicitly mentions what it does (distribution of clinical trial phases) and distinguishes it from sibling search/download tools by focusing on analysis rather than raw search or retrieval.

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 usage by indicating it filters analysis by conditions, interventions, sponsors, and max_studies. However, it provides no explicit guidance on when to use this tool versus alternatives like search_trials_by_condition or search_trials_by_intervention, and lacks any when-not or alternative recommendations.

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