clinical_trials_size_stats

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

Annotations already include readOnlyHint: true, indicating safe read operation. Description adds the type of output but no behavioral traits beyond that (e.g., no mention of pagination, caching, or rate limits). Since annotations cover safety profile, a score of 3 is appropriate; description adds some context but not rich behavioral detail.

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?

Description is two sentences, front-loaded with the main action, and contains no redundant words. Every sentence adds value, making it efficient and clear.

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 the tool has no parameters and no output schema, the description fully conveys what the tool returns (total study count, average JSON size, size distribution, largest studies) and its purpose (quick overview of database scope and volume). No additional detail is needed for this simple tool.

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?

Tool has no parameters (input schema empty). Schema coverage is 100% as there are no parameters to describe. Baseline for zero parameters is 4, and description adds no parameter info because none exist.

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?

Description clearly states it gets database statistics (total study count, average size, size distribution, largest studies) and provides a quick overview of ClinicalTrials.gov database scope and data volume. The verb 'Get' specifies action, and the resource 'database statistics' is distinct from sibling tools that search, detail, or retrieve results.

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?

Description implies usage for a quick overview, but lacks explicit when-to-use or when-not-to-use guidance compared to sibling tools like clinical_trials_search or clinical_trials_detail. No alternatives or exclusions are mentioned, so the agent must infer context from the tool's name and focus on statistics.

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