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

Annotations already declare readOnlyHint=true, openWorldHint=true, and idempotentHint=true, which establishes the safety and idempotency profile. The description adds meaningful behavioral context by stating it fetches no study data and is 'fast and lightweight', which helps an agent reason about performance and side-effect-free execution. This goes beyond the annotations without contradicting them.

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 three sentences, each earning its place. It front-loads the purpose, states the key distinction ('without fetching study data'), and then gives concrete use-case guidance. There is no filler, repetition, or unnecessary context. This is a model of conciseness.

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 11-parameter schema (all optional, all fully documented in the schema) and the presence of an output schema, the description is complete for its role. It tells an agent what the tool does, when to use it, and that it avoids heavy data fetching. All edge cases (e.g., empty filter lists, bracket syntax) are covered by the schema itself, so the description does not need to repeat them.

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% — every parameter has a detailed description covering syntax, valid values, and filtering behavior (e.g., phaseFilter, statusFilter, advancedFilter). The tool description adds no additional parameter semantics beyond what the schema already provides. Since the schema carries the full burden of parameter documentation, the baseline 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 a specific verb ('Get'), a resource ('total clinical trial study count from ClinicalTrials.gov'), and a key scope ('matching a query, without fetching study data'). This distinguishes it from siblings like clinicaltrials_search_studies (which returns full study records) and clinicaltrials_get_study_record (single study), so an agent can tell them apart without inspecting schemas.

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 gives concrete usage guidance: 'Use for quick statistics or to build breakdowns by calling multiple times with different filters' with examples (count by phase, status, recruiting vs completed). It clearly implies this is for counting rather than data retrieval, though it does not explicitly name alternative tools like clinicaltrials_search_studies for fetching data. The context is clear enough for appropriate routing.

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