clinical_trials_size_stats

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds context about what the tool returns (total study count, average JSON size, size distribution, largest studies), which is useful but not rich. It doesn't contradict the annotations. The description doesn't disclose any performance characteristics, data freshness, or limitations (e.g., how 'size' is measured or whether results are cached). With the safety profile covered by annotations, a 3 is appropriate—the description adds some value but not deep behavioral context.

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 two sentences with no filler. The first sentence front-loads the concrete deliverables (count, average size, size distribution, largest studies), and the second adds a quick contextual framing about scope and data volume. The 'quick overview' phrase in the second sentence is slightly redundant with the first sentence's enumeration but reinforces the tool's lightweight nature. No wasted words overall, though the second sentence could arguably be trimmed.

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?

For a zero-parameter tool with no output schema, the description carries the burden of explaining what the tool returns, which it does reasonably well by enumerating the four outputs. The main gap is the failure to differentiate from the sibling 'clinical_trials_stats' and the absence of any note about data freshness or update frequency, which matters for a database-statistics tool. Given the tool's simplicity, the description is mostly adequate but leaves the sibling-ambiguity question unresolved, which an agent would need to resolve on its own.

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 tool has zero parameters, making schema coverage trivially 100%. With no parameters to document, the baseline is 4, and the description appropriately focuses on describing the tool's outputs rather than parameter syntax. The enumeration of what the tool returns (count, average size, distribution, largest studies) substitutes for parameter documentation and helps the agent understand the result shape. Nothing is missing in terms of parameter semantics since there are no inputs to clarify.

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 with a specific verb ('Get') and resource ('database statistics'), enumerating concrete outputs: total study count, average study JSON size, size distribution, and largest studies. The first sentence is informative and specific. However, it fails to differentiate this tool from the nearly identical sibling 'clinical_trials_stats', which likely serves a similar statistical purpose. The 'size' focus is evident in the name but not explicitly highlighted in the description to distinguish it.

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 offers minimal usage context, noting it provides a 'quick overview of the ClinicalTrials.gov database scope and data volume.' This implies when to use it (for database-level overviews) but provides no explicit when-to-use vs when-not-to-use guidance and no exclusions. Critically, it never mentions or contrasts the very similar sibling 'clinical_trials_stats', leaving an agent to guess which statistical tool to invoke for a given task. For a tool with such a close sibling, the absence of routing guidance is a significant gap.

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